Compiling Question
Posted: 28.02.2006, 12:20
Since the new files with the gettext support for Win32, the proper libraries and includefiles for it, compiling and linking works fine with VC++ Toolkit 2003.
If I want to do the same with the VS7.0 IDE application and with the /MD switch set linking doesn't work.(multi-threathing-DLL-msvcrt.lib)
The only way I can compile and link Celestia is with the /ML switch set and with the option /nodefaultlib:"libcmt.lib; msvcrt.lib". This to avoid any conflict with declared functions in other libraries (e.g. Libc.lib.)
Question: Is this normal?
I check these options with the command line nmake tool.
I've found out that Celestia will build too without the MFLAGS=-MD option.
Question: what is the exact function of MFLAGS=-MD?
This option is set in winbuild.mak and passed to all the *.mak files in the subdirectories.
But the *.mak files still have the /ML option set.
Question: Does the MD-option in winbuild.mak overrules the /ML option?
Question: Maybe too premature but how do we link the *.po files with celestia?
If I want to do the same with the VS7.0 IDE application and with the /MD switch set linking doesn't work.(multi-threathing-DLL-msvcrt.lib)
The only way I can compile and link Celestia is with the /ML switch set and with the option /nodefaultlib:"libcmt.lib; msvcrt.lib". This to avoid any conflict with declared functions in other libraries (e.g. Libc.lib.)
Question: Is this normal?
I check these options with the command line nmake tool.
I've found out that Celestia will build too without the MFLAGS=-MD option.
Question: what is the exact function of MFLAGS=-MD?
This option is set in winbuild.mak and passed to all the *.mak files in the subdirectories.
But the *.mak files still have the /ML option set.
Question: Does the MD-option in winbuild.mak overrules the /ML option?
Question: Maybe too premature but how do we link the *.po files with celestia?