Dirk Reiners wrote:
Hi All,
Marcus Lindblom wrote:
Thiago Bastos wrote:
Hi all,
I'm having a bit of a hard time trying to follow the
nomenclature/installation standards in effect on OpenSG 2.0 (revision
1684).
First, the install directory for libs differ on Windows and Linux. On
Linux the Release libs go to "lib", the Debug libs go to "lib/debug"
and the DebugRT libs go to "lib/debugrt". On Windows the libs go to
"lib/opt", "lib/dbg" and "lib/debugrt", respectively.
Second, I think it's a bit problematic to have both the Release and
Debug libs with the same name. It would be preferable to have the libs
in the same dir with different suffixes, so we wouldn't need to update
any environment variable (PATH/LD_LIBRARY_PATH) to switch between the
Debug and Release version of our applications.
I just want to chip in that I second this. Every setting should have a
different suffix, so it's easy to select between them.
And another wish is to have _all_ builds generate pdb files, regardless
of their optimizations status.
I guess this is a bit of a Linux/Windows fight. Personally I like the
ability to just change the LD_LIBRARY_PATH to switch from release to
debug if I have to, without having to recompile my app. But to do that
the .sos need to have the same name. Am I the only one who cares about that?
I suspected that use case existed. It might be good for some windows
users as well, but I doubt it.
Could that be solved by extra links on linux, to the differently named
libs?
I understand the Windows convention is different, which is where the
problem with a single build system comes in.
Just to make sure I got things right (which I probably don't), we
currently have three versions:
debugrt - no optimizations, debugging info, debug runtime on windows, _d
suffix
debug - no optimizations, debugging info, release runtime on windows, no
suffix
release - optimizations, no debug info, release runtime on windows, no
suffix
So, debug/release are named the same and can be interchanged, and both
use the release c-runtime.
This naming is _very_ confusing to windows users, as something called
'debug' always uses the debug runtimes. Perhaps that's part of Thiago's
confusion above?
Given that, I could live with them having the same name. (I still have
to figure out how to take advantage of that in our build system... some
user-settable option during the configure/setup pass perhaps?.. hm.)
Also, please generate debug info for the release version too. (Stripped
pdb:s are ok, the call stack is all that matters and the locals are
seldom meaningful with optimizations on).
Cheers,
/Marcus
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Opensg-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-core
