Nice read. Also if interested this is how I got my ideas for the static qt link ->http://www.formortals.com/build-qt-stat ... c-compiler
It also contains useful info in the comments.
What is ASLR and what is it supposed to do?
Something irrelevant: I think the configure script for qbittorrent isn't very good. Sure it works on Linux but it isn't very flexible. If I remember correctly it doesn't let you choose the paths for qt/boost/libtorrent but it just checks the system libs and nothing else.(which is good for basic compilation). And on the Windows front, I haven't tried it but I suspect that it sucks big time. I wonder what are the possibilities to make it work better? Too much effort needed?
Trying out new gcc 4.7.x builds with lto and size optimizations
-
sledgehammer_999
- Administrator
- Posts: 2443
- Joined: Sun Jan 23, 2011 1:17 pm
Re: Trying out new gcc 4.7.x builds with lto and size optimizations
Last edited by sledgehammer_999 on Thu Nov 22, 2012 9:49 pm, edited 1 time in total.
-
Dayman
Re: Trying out new gcc 4.7.x builds with lto and size optimizations
ASLR stands for Address space layout randomization. It's not really necessary, especially on windows, but my paranoia kicks in from time to time.
The configure script itself shouldn't "let choose" anything except options related to building qBt. Choosing libs is usually done through pkg-config.
On windows configure script is not needed (it will work only under msys anyway) - you can do everything through qmake and qmake variables.
The configure script itself shouldn't "let choose" anything except options related to building qBt. Choosing libs is usually done through pkg-config.
On windows configure script is not needed (it will work only under msys anyway) - you can do everything through qmake and qmake variables.
-
sledgehammer_999
- Administrator
- Posts: 2443
- Joined: Sun Jan 23, 2011 1:17 pm
Re: Trying out new gcc 4.7.x builds with lto and size optimizations
[quote="Dayman"]
The configure script itself shouldn't "let choose" anything except options related to building qBt. Choosing libs is usually done through pkg-config.
On windows configure script is not needed (it will work only under msys anyway) - you can do everything through qmake and qmake variables.
[/quote]
Yes the correct and by default behavior should be "use pkg-config". But it should let you override the system libs and point it to custom built libs (eg for static linkage).
Yup, I forgot that using configure with MSVC isn't possible. Although a better version for MSYS would be great for a future transition to gcc builds.
I too like "automated" builds
.
The configure script itself shouldn't "let choose" anything except options related to building qBt. Choosing libs is usually done through pkg-config.
On windows configure script is not needed (it will work only under msys anyway) - you can do everything through qmake and qmake variables.
[/quote]
Yes the correct and by default behavior should be "use pkg-config". But it should let you override the system libs and point it to custom built libs (eg for static linkage).
Yup, I forgot that using configure with MSVC isn't possible. Although a better version for MSYS would be great for a future transition to gcc builds.
I too like "automated" builds
.-
Dayman
Re: Trying out new gcc 4.7.x builds with lto and size optimizations
[quote="sledgehammer_999"]
Yes the correct and by default behavior should be "use pkg-config". But it should let you override the system libs and point it to custom built libs (eg for static linkage).
[/quote]
AFAIK you need to have correct path to qmake in $PATH or use something like update-alternatives in ubuntu. qmake always knows where Qt libs and includes are. Everything else should be achievable with qmake's LIB and INCLUDE variables (just like we do on windows in winconf-*.pri); those can be specified on cmd line when invoking qmake.
Not sure why one might need static linux builds. Linux has no troubles with libraries in comparison to windows (every app ships it's own set of libs, plus WinxSys contains a crapload of system libs of all possible versions - 10.5 Gigs on my PC).
[quote="sledgehammer_999"]
Yup, I forgot that using configure with MSVC isn't possible. Although a better version for MSYS would be great for a future transition to gcc builds.
[/quote]
Actually mozilla build environment (based on MSYS) seems to support MSVC https://developer.mozilla.org/en-US/doc ... requisites
But i don't know if you can build something different from their browser with this environment
Anyway the only thing I build in MSYS is OpenSSL compiled with gcc.
Yes the correct and by default behavior should be "use pkg-config". But it should let you override the system libs and point it to custom built libs (eg for static linkage).
[/quote]
AFAIK you need to have correct path to qmake in $PATH or use something like update-alternatives in ubuntu. qmake always knows where Qt libs and includes are. Everything else should be achievable with qmake's LIB and INCLUDE variables (just like we do on windows in winconf-*.pri); those can be specified on cmd line when invoking qmake.
Not sure why one might need static linux builds. Linux has no troubles with libraries in comparison to windows (every app ships it's own set of libs, plus WinxSys contains a crapload of system libs of all possible versions - 10.5 Gigs on my PC).
[quote="sledgehammer_999"]
Yup, I forgot that using configure with MSVC isn't possible. Although a better version for MSYS would be great for a future transition to gcc builds.
[/quote]
Actually mozilla build environment (based on MSYS) seems to support MSVC https://developer.mozilla.org/en-US/doc ... requisites
But i don't know if you can build something different from their browser with this environment
Anyway the only thing I build in MSYS is OpenSSL compiled with gcc.