[jamming] xxx already defined in lib, ignoring second definition
fa658021 at skynet.be
Wed Feb 11 19:26:30 PST 2004
Hi everybody !
First of all thanks a lot to Paul and Randy :) I managed to fix my LOCATE_TARGET problem ( in case you're curious, the project is way too big to specify every .cpp file by hand, so I was "harvesting" them from predefined dirs, and I was passing them to Library with path attached, which caused LOCATE_TARGET to not be set properly. I fixed it by stripping the paths from the source files passed to Library and using SEARCH_SOURCE instead :p )
Now I'm back with another question for you Jam Gurus :) I remember reading something about this in the jamming archive, but google searches didn't turn anything up and I can't find it in the archive by hand anymore, so my apologies for posting this again :
If for example I build mylib.lib using mysource.cpp that has a function myfunction(), then re-build mylib.lib without doing a jam clean first, I get the following warnings :
(roughly, I'm at home now and forgot to mail myself the exact error messages)
warning : myfunction() already defined in mylib.lib, ignoring second definition.
Am I right to assume from this message that the old code for myfunction() is not being replaced by the new code for myfunction() ? Any ideas on how to fix this ?
As usual any help would be highly appreciated :) Thanks :)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the jamming