[boost] Re: [filesystem] WIN32 Can not use drive name in directory

From: David Daeschler (daveregs_at_[hidden])
Date: 2005-05-27 07:44:30

Good Morning (EST)

Okay, I came in this morning and pulled off the build command lines from the 
test build and from the full build.  This is what I came up with

-- Full Build

..snip..
"g++"   -c -Wall -ftemplate-depth-255   -g -O0 -fno-inline -mno-cygwin   -I"bin\boost\libs\filesystem\build" 
 -I"d:\srcbuilds\boost_1_32_0"   -I "d:\srcbuilds\boost_1_32_0"  -o 
"bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\runtime-link-static\path_posix_windows.obj" 
"d:\srcbuilds\boost_1_32_0\libs\filesystem\build\../src/path_posix_windows.cpp"

..snip..

"d:\MinGW\bin\ar.exe"  ru 
"bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\runtime-link-static\libboost_filesystem-mgw-sd-1_32.lib" 
"bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\runtime-link-static\exception.obj" 
"bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\runtime-link-static\operations_posix_windows.obj" 
"bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\runtime-link-static\path_posix_windows.obj" 
"bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\runtime-link-static\convenience.obj"
..snip..

-- Test Build

..snip..
"g++"   -c -Wall -ftemplate-depth-255   -g -O0 -fno-inline -mno-cygwin   -I"..\..\..\bin\boost\libs\filesystem\build" 
 -I"d:\srcbuilds\boost_1_32_0"   -I "d:\srcbuilds\boost_1_32_0"  -o 
"..\..\..\bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\path_posix_windows.obj" 
"d:\srcbuilds\boost_1_32_0\libs\filesystem\build\../src/path_posix_windows.cpp"

..snip..

"d:\MinGW\bin\ar.exe"  ru 
"..\..\..\bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\libboost_filesystem-mgw-d-1_32.lib" 
"..\..\..\bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\exception.obj" 
"..\..\..\bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\operations_posix_windows.obj" 
"..\..\..\bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\path_posix_windows.obj" 
"..\..\..\bin\boost\libs\filesystem\build\libboost_filesystem.lib\mingw\debug\convenience.obj"
..snip..

As you can see the commands are the same as far as parameters that would 
affect the build.

So the insight came when I linked to the built filesystem static library 
instead of the DLL.  It appears that when I statically link the filesystem 
lib in it works fine, but when I let g++ dynamically link to the DLL 
(using -l ) it tells me that c:\ is an invalid path.

"David Abrahams" <dave_at_[hidden]> wrote in message 
news:u3bs9iq0k.fsf_at_boost-consulting.com...
> "David Daeschler" <daveregs_at_[hidden]> writes:
>
>> Hello again,
>>
>>>You can pass --preserve-test-targets to bjam to suppress that behavior.
>>
>> Ha, that's easier then hitting ctrl+c in the middle of the build, thanks 
>> :).
>>
>>>  So what is the difference in command-line options vs. whatever you
>>> invoked to build/run the boost regression tests
>>
>> To build the regression I go to lib/filesystem/test and run [ bjam
>> "-sTOOLS=mingw" ] without the stage.
>
> Of course. I mean the command-line options issued to the compiler by
> bjam in each case.
>
>
> -- 
> Dave Abrahams
> Boost Consulting
> www.boost-consulting.com
>
> _______________________________________________
> Unsubscribe & other changes: 
> http://lists.boost.org/mailman/listinfo.cgi/boost
>