On Jan 15, 2008 9:17 PM, Jonathan Turkanis wrote:

Chris Miller wrote:

...

Why on earth I try and support Windows is beyond my comprehension. It's just something I do.

I'm having some massive difficulties making Boost build with MinGW so I can start using it from Code::Blocks. I've tried using Boost's native Jam system, but first I have to build that.

You don't have to build it; you can download a pre-built binary: http://tinyurl.com/2q36f.

For MinGW/Windows Vista, which one would I pick? I picked the "platform independent" one, which didn't work.

...

And that doesn't work.

It keeps telling me this:

...

...

It keeps trying to use the MSVC toolset, even though I'm telling it not to.

Any help here would be nice!

Have you tried:

set PATH= build mingw

?

That's not what the build instructions said. They said to use build.bat mingw, 'cause that's my toolkit. It kept trying it with MSVC for some odd reason. http://mindofsauron.blogspot.com/2008/01/boost-me-up.html -- Registered Linux Addict #431495 http://profile.xfire.com/mrstalinman John 3:16! If Microsoft is the Wal*Mart of the Software World, then Linux is the Home Depot

On Jan 15, 2008 10:01 PM, Jonathan Turkanis wrote:

Chris Miller wrote:

...

On Jan 15, 2008 9:17 PM, Jonathan Turkanis wrote:

...

Chris Miller wrote:

...

Why on earth I try and support Windows is beyond my comprehension. It's just something I do.

I'm having some massive difficulties making Boost build with MinGW so I can start using it from Code::Blocks. I've tried using Boost's native Jam system, but first I have to build that. You don't have to build it; you can download a pre-built binary: http://tinyurl.com/2q36f.

For MinGW/Windows Vista, which one would I pick?

I assume boost-jam-3.1.16-1-ntx86.zip

Oh, silly me. NT x86... I keep forgetting I'm using a NT kernel. Microsoft and their weird naming systems. I think it's wiser for me to learn how to build it from source, however. What if I run into binary compatibility issues after a GCC upgrade? I know it's probably not an issue, but I also want to make the build setup process harder as a project leader to try and filter out the faint of heart. The moment you say "game" in a programming forum there are many people interested, but very rarely do you find someone with the drive to see it through.

...

I picked the "platform independent" one, which didn't work.

Needless to say, the platform independent download is not one of the pre-built binaries.

...

...

...

Any help here would be nice! Have you tried:

set PATH= build mingw

?

That's not what the build instructions said. They said to use build.bat mingw, 'cause that's my toolkit. It kept trying it with MSVC for some odd reason.

It shouldn't matter which toolset you use to build bjam. The resulting executable will still work with MinGW.

I thought it was only C that had a binary layout contract or whatever they call it. That's cool, though off topic, how does that work?

If you read Building Bjam (http://www.boost.org/doc/html/jam/building.html), you will see that running

bjam <toolset-name>

requires that the compiler be in your PATH. In addition, I've found that having other compilers in my PATH sometimes confuses build.bat.

I just enforced that PATH variable after my last shutdown. I'm at school and on my Kubuntu laptop now, but when I get home this is going to be one of my first things after homework. Should I add MSYS to the PATH as well, or do you think that will be necessary? I have MSYS installed, I'm just not sure. I don't have MSVC installed, nor have I ever had it installed on this OS, so I wonder why it picked MSVC. Wait a sec... maybe because it wasn't exported to the PATH it didn't apply in the batch file? So next boot it should work? Perhaps. It'll be interesting to write that down on the wiki... Thanks for the help! -- Registered Linux Addict #431495 http://profile.xfire.com/mrstalinman John 3:16! If Microsoft is the Wal*Mart of the Software World, then Linux is the Home Depot

Oops... I missed reading this thread... With "C:\MinGW\bin", or wherever you have the mingw gcc.exe, in your "PATH" doing:

echo %Path% cd \location\of\jam\src .\build.bat mingw

Produces for me: C:\DevRoots\Boost\boost\tools\jam\src>echo %Path% C:\Python24\.;c:\MinGW\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program Files\Common Files\GTK\2.0\bin;C:\Boost\bin;C:\Boost\lib;C:\Pr ogram Files\PuTTY;C:\Program Files\Perforce;C:\Program Files\QuickTime\QTSystem\;C:\Perl\bin;C:\Program Files\GnuWin32\bin;C:\Program Files\doxygen\bi n;C:\Program Files\Common Files\Adobe\AGL;C:\Program Files\Subversion\bin;C:\Bin;C:\DevRoots\RSI\org\stlport\STLport\bin;C:\KDE\bin C:\DevRoots\Boost\boost\tools\jam\src>.\build.bat mingw ### ### Using 'mingw' toolset. ### C:\DevRoots\Boost\boost\tools\jam\src>rd /S /Q bootstrap C:\DevRoots\Boost\boost\tools\jam\src>md bootstrap C:\DevRoots\Boost\boost\tools\jam\src>gcc -DNT -o bootstrap\jam0.exe command.c compile.c debug.c execnt.c expand.c filent.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c output.c parse.c pathunix.c regexp.c rules.c scan.c search.c subst.c time stamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c w32_getreg.c native.c modules/set.c modules/path.c modules/regex.c modules/ property-set.c modules/sequence.c modules/order.c C:\DevRoots\Boost\boost\tools\jam\src>.\bootstrap\jam0 -f build.jam --toolset=mingw "--toolset-root= " clean ...found 1 target... ...updating 1 target... [DELETE] clean ...updated 1 target... C:\DevRoots\Boost\boost\tools\jam\src>.\bootstrap\jam0 -f build.jam --toolset=mingw "--toolset-root= " ...found 47 targets... ...updating 1 target... [COMPILE] bin.ntx86\bjam.exe ...updated 1 target... -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

On Jan 16, 2008 2:32 PM, Jonathan Turkanis wrote:

Rene Rivera wrote:

...

Oops... I missed reading this thread...

With "C:\MinGW\bin", or wherever you have the mingw gcc.exe, in your "PATH" doing:

...

echo %Path% cd \location\of\jam\src .\build.bat mingw

Produces for me:

...

[COMPILE] bin.ntx86\bjam.exe ....updated 1 target...

Works for me too. I'm pretty sure the problem was with PATH.

It begs to differ. C:\USERS\LORDSA~1\DESKTOP\BOOSTJAM>build.bat mingw ### ### Using 'msvc' toolset. ### C:\Users\LORDSA~1\DESKTOP\BOOSTJAM>rd /S /Q bootstrap C:\Users\LORDSA~1\DESKTOP\BOOSTJAM>md bootstrap C:\Users\LORDSA~1\DESKTOP\BOOSTJAM>cl /nologo /GZ /Zi /MLd /Fobootstrap/ /Fdboot strap/ -DNT -DYYDEBUG kernel32.lib advapi32.lib user32.lib /Febootstrap\jam0 co mmand.c compile.c debug.c execnt.c expand.c filent.c glob.c hash.c hdrmacro.c he aders.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c outpu t.c parse.c pathunix.c regexp.c rules.c scan.c search.c subst.c timestamp.c vari able.c modules.c strings.c filesys.c builtins.c pwd.c class.c w32_getreg.c nativ e.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules /sequence.c modules/order.c 'cl' is not recognized as an internal or external command, operable program or batch file. C:\USERS\LORDSA~1\DESKTOP\BOOSTJAM>PATH PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\PROGRA~1\QUICKT~ 1\QTSystem\;C:\MinGW\bin C:\USERS\LORDSA~1\DESKTOP\BOOSTJAM> Perhaps because it uses the executables "mingw32-*" instead of the plain names? C:\USERS\LORDSA~1\DESKTOP\BOOSTJAM>dir c:\MinGW\bin Volume in drive C has no label. Volume Serial Number is 3071-688E Directory of c:\MinGW\bin 01/15/2008 06:29 PM <DIR> . 01/15/2008 06:29 PM <DIR> .. 08/24/2006 09:35 PM 559,577 addr2line.exe 07/22/2007 04:49 AM 2,388,304 alld42.dll 07/22/2007 04:51 AM 1,032,582 alleg42.dll 07/22/2007 04:50 AM 1,043,258 allp42.dll 08/24/2006 09:35 PM 525,951 ar.exe 08/24/2006 09:35 PM 792,360 as.exe 01/18/2006 12:04 PM 92,160 c++.exe 08/24/2006 09:35 PM 558,024 c++filt.exe 01/18/2006 12:05 PM 91,648 cpp.exe 08/24/2006 09:35 PM 611,153 dlltool.exe 08/24/2006 09:35 PM 63,213 dllwrap.exe 01/18/2006 12:04 PM 92,160 g++.exe 01/18/2006 12:06 PM 89,600 gcc.exe 01/18/2006 12:05 PM 16,031 gccbug 01/18/2006 12:05 PM 26,112 gcov.exe 08/24/2006 09:35 PM 625,174 gprof.exe 08/24/2006 09:35 PM 806,237 ld.exe 01/18/2006 12:04 PM 92,160 mingw32-c++.exe 01/18/2006 12:04 PM 92,160 mingw32-g++.exe 01/18/2006 12:06 PM 89,600 mingw32-gcc-3.4.5 01/18/2006 12:06 PM 89,600 mingw32-gcc.exe 03/21/2007 08:53 AM 166,400 mingw32-make.exe 08/03/2007 04:08 PM 11,673 mingwm10.dll 08/24/2006 09:35 PM 570,469 nm.exe 08/24/2006 09:35 PM 717,083 objcopy.exe 08/24/2006 09:35 PM 849,949 objdump.exe 08/24/2006 09:35 PM 525,951 ranlib.exe 08/24/2006 09:35 PM 268,447 readelf.exe 08/24/2006 09:35 PM 508,399 size.exe 08/24/2006 09:35 PM 507,802 strings.exe 08/24/2006 09:35 PM 717,083 strip.exe 08/24/2006 09:35 PM 617,067 windres.exe 32 File(s) 15,237,387 bytes 2 Dir(s) 86,189,252,608 bytes free C:\USERS\LORDSA~1\DESKTOP\BOOSTJAM> but wait, I see the plain names there as well... that's strange. Now I'm confused. I don't even have a theory now. I hate to go all OS 8.9, but EEP! -- Registered Linux Addict #431495 http://profile.xfire.com/mrstalinman John 3:16! If Microsoft is the Wal*Mart of the Software World, then Linux is the Home Depot

On Jan 16, 2008 8:54 PM, Jonathan Turkanis wrote:

Chris Miller wrote:

...

On Jan 16, 2008 2:32 PM, Jonathan Turkanis wrote:

...

...

Works for me too. I'm pretty sure the problem was with PATH.

It begs to differ.

<snip>

I guess I spoke too soon. With your PATH, it looks to me like "build.bat mingw" should work.

I opened up build.bat to see what was going on, and discovered that Rene is the author, so I'll let him take over :)

Good luck!

It's a batch file, I'll need all the luck I can get. Were it bash I'd have a fighting chance, but my DOS is so rusty... yeah, pretty dang scary. -- Registered Linux Addict #431495 http://profile.xfire.com/mrstalinman John 3:16! If Microsoft is the Wal*Mart of the Software World, then Linux is the Home Depot

On 1/17/08, Rene Rivera wrote:

Chris Miller wrote:

...

On Jan 16, 2008 8:54 PM, Jonathan Turkanis wrote:

...

Chris Miller wrote:

...

On Jan 16, 2008 2:32 PM, Jonathan Turkanis wrote:

...

Works for me too. I'm pretty sure the problem was with PATH. It begs to differ. <snip>

I guess I spoke too soon. With your PATH, it looks to me like "build.bat mingw" should work.

I opened up build.bat to see what was going on, and discovered that Rene is the author, so I'll let him take over :)

Good luck!

It's a batch file, I'll need all the luck I can get. Were it bash I'd have a fighting chance, but my DOS is so rusty... yeah, pretty dang scary.

I should ask the rather obvious... Which version of Bjam are you trying to compile?

Version 3.1.16 (http://downloads.sourceforge.net/boost/boost-jam-3.1.16.zip?modtime=1196632872&big_mirror=0) -- Registered Linux Addict #431495 http://profile.xfire.com/mrstalinman John 3:16! If Microsoft is the Wal*Mart of the Software World, then Linux is the Home Depot

Hi Chris I have also built some binaries for Boost on MinGW. You can download them here: http://ascendwiki.cheme.cmu.edu/Binary_installer_for_Boost_on_MinGW I can provide the installer scripts etc if anyone's interested. I have built against these libraries and linked etc using SCons, but I'm sure other tools will do it too. Cheers JP Chris Miller wrote:

On Jan 15, 2008 9:17 PM, Jonathan Turkanis wrote:

...

Chris Miller wrote:

...

Why on earth I try and support Windows is beyond my comprehension. It's just something I do.

I'm having some massive difficulties making Boost build with MinGW so I can start using it from Code::Blocks. I've tried using Boost's native Jam system, but first I have to build that.

You don't have to build it; you can download a pre-built binary: http://tinyurl.com/2q36f.

For MinGW/Windows Vista, which one would I pick? I picked the "platform independent" one, which didn't work.

...

...

And that doesn't work.

It keeps telling me this:

...

...

It keeps trying to use the MSVC toolset, even though I'm telling it not to.

Any help here would be nice!

Have you tried:

set PATH= build mingw

?

That's not what the build instructions said. They said to use build.bat mingw, 'cause that's my toolkit. It kept trying it with MSVC for some odd reason.

http://mindofsauron.blogspot.com/2008/01/boost-me-up.html

-- John Pye http://pye.dyndns.org/