trying to build standalone app
-
Hi @mzimmers ,
Just to add one important piece for dynamic linking on Windows, which was not explicited state before, I think:
- The
*.libfile is needed at link time, it does not need to be deployed with the application - The
*.dllfile is needed at run time, it needs to be deployed
- The
-
Hi @mzimmers ,
Just to add one important piece for dynamic linking on Windows, which was not explicited state before, I think:
- The
*.libfile is needed at link time, it does not need to be deployed with the application - The
*.dllfile is needed at run time, it needs to be deployed
@aha_1980 said in trying to build standalone app:
Hi @mzimmers ,
Just to add one important piece for dynamic linking on Windows, which was not explicited state before, I think:
- The
.libfile is needed at link time, it does not need to be deployed with the application - The
*.dllfile is neede at run time, it needs to be deployed
@koahnig said in trying to build standalone app:
@mzimmers
For windows, either you have one lib or you have a lib and a dll. If you got both you need the lib for liniking and the dll for execution.I acknowledge, a bit hidden ;)
- The
-
Still fooling around with this...I borrowed the code below from somewhere:
myown_installs.files = "C:/Program Files (x86)/Expat 2.2.5/Bin/libexpat.lib" \ "C:/Program Files (x86)/Expat 2.2.5/Bin/libexpat.dll" myown_installs.path = $$OUT_PWD/releaseWhich works fine for my builds to the /release subdirectory, but not for debugs. Is there some clever way to conditionalize this in my project file?
-
Hi,
Are you trying to make a standalone debug application ?
-
Ok, I see. Then use
CONFIG(debug, debug|release){ # Debug specific stuff } else { # Release specific stuff } -
You have a
}just afterrelease. -
No worries, things like that happen ;)