RE: [Boost-Users] RE: [date_time] library binaries for VC7.1? && Comm on lib placement
Dan, At least, so far, it only allows for debug/non-debug tagging. Right now, I'm starting to get involved over on the Boost.Build <http://groups.yahoo.com/group/jamboost/> mailing list. We'll see exactly how things pan out, although I doubt there will be any major changes for a little while. Dale
-----Original Message----- From: Dan Muller [mailto:yg-boost-users@m.gmane.org] Sent: Monday, August 18, 2003 6:00 AM To: boost-users@yahoogroups.com Subject: [Boost-Users] RE: [date_time] library binaries for VC7.1? && Comm on lib placement
In article <41B553DE6D81D5119AD90050DA7ACF702E62E6@PDCSERVER>, administrator@sbcltd.com says...
Dan,
The date_time.lib library is a static lib. The built date_time.dll actually has no exports in it, so for VC purposes is useless. I would say don't worry about it, and just use the static lib.
Thanks, Dale, this is exactly what I needed to know. I was starting to worry that I didn't understand DUMPBIN's output, which would be worrisome since I've been using it for years. :-)
On a side note, has anyone been working on placing built items into a common directory, say <boost_top_dir>/lib?
If not, I have a patch that should help alot.
Sounds like an excellent idea. I'm assuming that on Windows, the boost build would then follow common conventions so that libraries built with different characteristics (debug vs. non-debug, multi- vs. single- threaded, etc) had different names. (I haven't been following boost build developments lately -- is this a topic of ongoing changes?)
-----Original Message----- From: Dan Muller [mailto:yg-boost-users@m.gmane.org]
[text elided]
After building boost for VC7.1, I find a .lib file in boost_1_30_0\libs\date_time\build\bin\libboost_date_time.lib\m svc\debug \runtime-link-dynamic and a .dll in
boost_1_30_0\libs\date_time\build
\bin\boost_date_time.dll\msvc\debug\runtime-link-dynamic.
There are a couple of things that I don't understand about these files.
Is the .lib file supposed to be the import library for the .dll? Linking against the .lib file hasn't produced any import references in my applications. Perhaps I'm just not hitting any out-of-line functionality, but it sure seems like the .lib file is a static library rather than an import library.
Also, running DUMPBIN /EXPORTS on the .dll file shows no exported symbols related to date_time classes, as far as I can see. It really looks like it's exporting a bunch of stuff related to the standard C++ library, which makes no sense to me.
-- Dan Muller "So that's what an invisible barrier looks like!" (Time Bandits)
------------------------ Yahoo! Groups Sponsor ---------------------~--> Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark Printer at Myinks.com. Free s/h on orders $50 or more to the US & Canada. http://www.c1tracking.com/l.asp?cid=5511 http://us.click.yahoo.com/l.m7sD/LIdGAA/qnsNAA/EbFolB/TM -------------------------------------------------------------- -------~->
Info: <http://www.boost.org> Wiki: <http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl> Unsubscribe: <mailto:boost-users-unsubscribe@yahoogroups.com>
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
In article <41B553DE6D81D5119AD90050DA7ACF702E62F0@PDCSERVER>, administrator@sbcltd.com says...
Dan,
At least, so far, it only allows for debug/non-debug tagging. Right now, I'm starting to get involved over on the Boost.Build <http://groups.yahoo.com/group/jamboost/> mailing list. We'll see exactly how things pan out, although I doubt there will be any major changes for a little while.
Thanks, I've start following that mailing list again. I know these are difficult problems to solve in a portable way; it will be interesting to see what people propose.
-----Original Message----- From: Dan Muller [mailto:yg-boost-users@m.gmane.org]
In article <41B553DE6D81D5119AD90050DA7ACF702E62E6@PDCSERVER>, administrator@sbcltd.com says...
Dan,
The date_time.lib library is a static lib. The built date_time.dll actually has no exports in it, so for VC purposes is useless. I would say don't worry about it, and just use the static lib.
Thanks, Dale, this is exactly what I needed to know. I was starting to worry that I didn't understand DUMPBIN's output, which would be worrisome since I've been using it for years. :-)
On a side note, has anyone been working on placing built items into a common directory, say <boost_top_dir>/lib?
If not, I have a patch that should help alot.
Sounds like an excellent idea. I'm assuming that on Windows, the boost build would then follow common conventions so that libraries built with different characteristics (debug vs. non-debug, multi- vs. single- threaded, etc) had different names. (I haven't been following boost build developments lately -- is this a topic of ongoing changes?)
-- Dan Muller "So that's what an invisible barrier looks like!" (Time Bandits)
participants (2)
-
Administrator -
Dan Muller