Solved 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
*.lib
file is needed at link time, it does not need to be deployed with the application - The
*.dll
file is needed at run time, it needs to be deployed
- The
-
@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
.lib
file is needed at link time, it does not need to be deployed with the application - The
*.dll
file 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/release
Which 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 ?
-
Hi - no, but when I try to run the debugger, it crashes because these files aren't in the build directory.
-
Ok, I see. Then use
CONFIG(debug, debug|release){ # Debug specific stuff } else { # Release specific stuff }
-
I get a very unexpected error from this:
Any idea what I'm doing wrong?
-
You have a
}
just afterrelease
. -
Oh, brother...I'd downvote myself for that if I could.
It works fine now...thanks, SGaist.
-
No worries, things like that happen ;)