Ian MacArthur wrote:
> What does the DLL build version of fluid do?
Release build of fluid.exe links against fltk.lib, so it's static.
I did a VS 2010 release build of FLTK; the build log shows it links
against fltk.lib, and 'depends fluid.exe' shows it has no dependency
on FLTK dlls.
> That works, afaik, as do the test programs, at least when I build
> them "dynamic" with mingw.
I don't think we have a build option that builds the test
programs against DLLs; I think the default is static currently.
I just checked the build log for input.exe, and it links against
fltk.lib (static):
1> C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\link.exe
/ERRORREPORT:PROMPT \
/OUT:"../../test/input.exe" /INCREMENTAL:NO /NOLOGO \
/LIBPATH:..\..\lib fltk.lib \ <--
*STATIC LINK AGAINST FLTK.LIB*
comctl32.lib kernel32.lib user32.lib gdi32.lib \
winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib
oleaut32.lib \
uuid.lib odbc32.lib odbccp32.lib /NODEFAULTLIB:libcd /MANIFEST \
/ManifestFile:".\input_release\input.exe.intermediate.manifest" \
/MANIFESTUAC:"level='asInvoker' uiAccess='false'" \
/PDB:".\input_release\input.pdb" /SUBSYSTEM:WINDOWS /TLBID:1 \
/DYNAMICBASE:NO /IMPLIB:"..\..\test\input.lib" /MACHINE:X86 \
.\input_release\input.obj
> I have no idea what the MS VS tools do,
> but it can't be all that different?
The whole WinMain() thing is probably unique to VS, which is I think
what's mainly biting asif here..
It seems like there's a special situation that happens currently
when you try to build a /subsystem:windows app with DLL linking
against fltk; WinMain isn't getting defined in FLTK, so the linker
throws an error about it not being defined.
The question I can't figure out is where should WinMain() be defined
in that case?
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
