On 2015/05/19 01:34 AM, Dale Marchand wrote:
Can someone explain why the following line in a .pro file fails to
create a softlink:
system(ln -s /home/marchand/test.xml /home/marchand/test2.xml)
but when the output is stored in a variable, the link is created as
expected:
Can someone explain why the following line in a .pro file fails to
create a softlink:
system(ln -s /home/marchand/test.xml /home/marchand/test2.xml)
but when the output is stored in a variable, the link is created as
expected:
THROW_AWAY_VAR=$$system(ln -s /home/marchand/test.xml
Hello,
I'm porting an application (xxdiff) to Qt5 that has a lex/yacc based parser on
board. The .pro file contains the following section:
#
# Parser/grammar generation.
#
QMAKE_LEX = flex
QMAKE_YACC = bison
QMAKE_YACCFLAGS = -d -o y.tab.c
QMAKE_YACC_HEADER = y.tab.h
QMAKE_YACC_SOURCE = y.tab.c
That is the very deffinition of 'difficult', no? The solution i found may
be a work around for the c++ version issues.
On Mar 25, 2015 7:45 PM, Thiago Macieira thiago.macie...@intel.com
wrote:
On Wednesday 25 March 2015 18:08:12 Tim O'Neil wrote:
Qmake with clang is possble, but its not easy;
On Friday 27 March 2015 15:18:27 Tim O'Neil wrote:
That is the very deffinition of 'difficult', no? The solution i found may
be a work around for the c++ version issues.
Clang with Linux isn't difficult. I use it every week and it's no different
from
ICC on Linux or GCC on Linux. Both are
Am 25.03.2015 um 06:28 schrieb Thiago Macieira:
On Wednesday 25 March 2015 06:19:24 Wilhelm wrote:
Hi all,
the qmake documentation says that is is possible to set
CONFIG+= c++14
But if I do so, the generated makefile still contains the flag
-std=c++11
So, whats wrong here?
Your
El Wednesday 25 March 2015, Wilhelm escribió:
Hi all,
the qmake documentation says that is is possible to set
CONFIG+= c++14
But if I do so, the generated makefile still contains the flag
-std=c++11
So, whats wrong here?
1. Have you re-rerun qmake?
2. Does your compiler support
Am 25.03.2015 um 07:52 schrieb Thiago Macieira:
On Wednesday 25 March 2015 07:24:10 Wilhelm wrote:
Your compiler is too old or the version was not detected.
Don't think so...
What's in mkspecs/qconfig.pri? I have here:
QT_GCC_MAJOR_VERSION = 4
QT_GCC_MINOR_VERSION = 9
Am 25.03.2015 um 12:03 schrieb Allan Sandfeld Jensen:
On Wednesday 25 March 2015, Wilhelm wrote:
Hi all,
the qmake documentation says that is is possible to set
CONFIG+= c++14
But if I do so, the generated makefile still contains the flag
-std=c++11
So, whats wrong here?
You can
On Wednesday 25 March 2015 14:46:52 Wilhelm wrote:
As you can see running qmake with linux-clang doesn't work:
⌁68% [lmeier:/home/lmeier/Lehre/Eigene/Prog2NeuesKonzept/SS2015/vl01] $
qmake -spec linux-clang
That will not work because you configured with GCC. qmake only knows the GCC
On Thursday 26 March 2015 06:07:24 Wilhelm wrote:
That looks strange to me: if I define several kits (with different
compilers like g++ and clang++ or ms vs) in qtcreator I would expect
that the CONFIG+=c++14 variable would be translated to the correct
compiler flag.
That's not how it works.
On Thursday 26 March 2015 06:49:50 Wilhelm wrote:
Am 26.03.2015 um 06:15 schrieb Thiago Macieira:
On Thursday 26 March 2015 06:07:24 Wilhelm wrote:
That looks strange to me: if I define several kits (with different
compilers like g++ and clang++ or ms vs) in qtcreator I would expect
that
On Wednesday 25 March 2015, Wilhelm wrote:
Hi all,
the qmake documentation says that is is possible to set
CONFIG+= c++14
But if I do so, the generated makefile still contains the flag
-std=c++11
So, whats wrong here?
You can check mkspecs/features/c++14.prf for the conditions
On Wednesday 25 March 2015 18:08:12 Tim O'Neil wrote:
Qmake with clang is possble, but its not easy; ths is a possble solution:
https://forum.qt.io/topic/19067/solved-using-qtcreator-qmake-with-clang-libc
It's not difficult at all. But in order to enable C++14, you need to have
compiled Qt
Hi all,
the qmake documentation says that is is possible to set
CONFIG+= c++14
But if I do so, the generated makefile still contains the flag
-std=c++11
So, whats wrong here?
--
Wilhelm
w.me...@unix.net
___
Interest mailing list
Sent: Saturday, March 21, 2015 at 2:23 PM
From: Thiago Macieira thiago.macie...@intel.com
To: interest@qt-project.org
Subject: Re: [Interest] qmake: mkspec linux-g++ not found
On Friday 20 March 2015 20:44:07 Jason H wrote:
I built Qt from sources, did a make install, then blew away
On Monday 23 March 2015 21:47:57 Jason H wrote:
Ok, so I got this figured out. Someone tell me if it is a bug or not.
I did not specify --prefix, however it built and installed as
--prefix=/usr/local/Qt-5.4.1 qmake however did not pick up the prefix that
had been auto selected. After running
Sent: Monday, March 23, 2015 at 11:08 AM
From: Jason H jh...@gmx.com
To: Thiago Macieira thiago.macie...@intel.com
Cc: interest@qt-project.org
Subject: Re: [Interest] qmake: mkspec linux-g++ not found
Sent: Saturday, March 21, 2015 at 2:23 PM
From: Thiago Macieira thiago.macie
On Monday 23 March 2015 16:08:50 Jason H wrote:
You need to use the installed qmake (in /usr/local/Qt-5.4.1/bin), not the
one in the build dir.
I was.
[ec2-user@PRODUCTION-WWW pdfReport]$ qmake
Could not find qmake configuration file linux-g++.
Error processing project file:
Hi,
How come that the bootstrap qmake ignores the mkspec's CMAKE_CC and CMAKE_CXX?
I see `/usr/bin/clang++` and `/Developer/usr/bin/clang` (for C and ObjC++) when
configure runs the config.test tests, and this causes problems because I need
to use the clang compiler specified in my mkspec.
On 20/03/15 21:44, Jason H wrote:
I built Qt from sources, did a make install, then blew away the source
directory.
I went into my project dir, did qmake and got that error.
I looked in /usr/local/Qt-5.4.1/mkspecs and there were the proper files there.
Then I un-blew away the source dir
On Friday 20 March 2015 20:44:07 Jason H wrote:
I built Qt from sources, did a make install, then blew away the source
directory. I went into my project dir, did qmake and got that error.
I looked in /usr/local/Qt-5.4.1/mkspecs and there were the proper files
there.
Then I un-blew away the
I built Qt from sources, did a make install, then blew away the source
directory.
I went into my project dir, did qmake and got that error.
I looked in /usr/local/Qt-5.4.1/mkspecs and there were the proper files there.
Then I un-blew away the source dir (cautious me, I did a move) and it all
Hi,
I have a little problem. I am cross compiling an application targeting
Android (in addition to Windows/Mac and Linux). However the
development of Android happens on both OSX and Windows.
Currently I have the following:
android {
message(Android)
DEFINES +=
We and may be many others would like to build iOS apps by CI systems like
Jenkins. We have been using Jenkins a long time but after code 6.1 there
appeared an issue. Signing app now requires Payload/*.app/ResourceRules.
plist
that must be defined in appname.xcodeproj file:
For setting launch images or app icons, this snippet just works for me:
ios {
AppIcons.files=$$system(find $$PWD/appicon/ios/ -name '*.png')
AppIcons.path=./
LaunchImages.files=$$system(find $$PWD/launchimage/ios/ -name '*.png')
LaunchImages.path=./
QMAKE_BUNDLE_DATA +=
Dear list,
I'm using qmake project files for a library project. On Linux with a
standard pathes for installed headers and libraries, there was rarely
the need to add a non-standard path. If that happened, a command line
assignment did the job:
qmake INCLUDEPATH+=C:/path/to/headers file.pro
I
Hey there,
I have a project which builds a plugin for a cross platform application.
This application expects its plugins to have the extension *.xpl. After
reading the docs and setting the qmake variables to
TARGET = plugin
TARGET_EXT=xpl
I expected to get a shared library called plugin.xpl. On
Den 18-06-2014 13:23, Roland Winklmeier skrev:
Hey there,
I have a project which builds a plugin for a cross platform application.
This application expects its plugins to have the extension *.xpl. After
reading the docs and setting the qmake variables to
TARGET = plugin
TARGET_EXT=xpl
I
unix:QMAKE_POST_LINK += cp $$DESTDIR/$$TARGET.so $$DESTDIR/$$TARGET.xpl
Written from memory, you probably need to fix it a bit.
I hope this helps,
Thanks Bo. You pointed me into the right direction.
CONFIG += plugin
unix:QMAKE_POST_LINK += mv $$DESTDIR/lib$${TARGET}.so
Den 18-06-2014 16:04, Roland Winklmeier skrev:
unix:QMAKE_POST_LINK += cp $$DESTDIR/$$TARGET.so $$DESTDIR/$$TARGET.xpl
Written from memory, you probably need to fix it a bit.
I hope this helps,
Thanks Bo. You pointed me into the right direction.
You're very welcome :)
As Thiago already pointed out - just run:
Thanks, noted. But I have some weird issue with interest mailing list. I
usually post to both development and interest in case I am confused
which mailing group does my question fall under, so what happens all the
time is the question posted on
Em qui 10 abr 2014, às 14:53:44, Sandeep escreveu:
Thanks, noted. But I have some weird issue with interest mailing list. I
usually post to both development and interest in case I am confused
which mailing group does my question fall under
Please stop doing that.
If you have a question about
Hello,
I have an application which links to Qt shared libraries. I build the
application with Qt creator, so I manually configure the qmake to be chosen
by the qtcreator. So all the qt libraries are automatically linked in
accordance to the qmake path.
Now after the application is built, I
qmake -v gives the below output:
QMake version 3.0
Using Qt version 5.0.2 in /usr/lib/x86_64-linux-gnu
But is there a qmake option or any other mechanism which can directly give
the value /usr/lib/x86_64-linux-gnu, otherwise I need to run qmake -v and
parse for the path.
As Thiago
On 02-Apr-14 09:55, tangk wrote:
win32:{
LIBS += $$PWD/living1.lib
system(copy $$PWD/living1.dll $$[QT_INSTALL_BINS])
}
The error is that you pass paths with forward slashes to the copy
command. Use the shell_path function to convert the slashes.
BR,
Joerg
Hi,
I want to run some commands in release build so I used the mentioned tip
in FAQ section
https://qt-project.org/faq/answer/how_to_deal_correctly_with_project_files_that_should_generate_a_debug_and_r
but unfortunately system function called in both DEBUG and RELEASE mode
How can I fix this
Dear all,
I sometimes experience problems with qmake (used in QtCreator). This
happens not often, but my program crashes after a partial build, and if I
rebuild all, it works perfectly.
This means some file dependencies are not handled well. Maybe my .pro has
some errors that cause this?
For
Em seg 24 fev 2014, às 17:41:44, Etienne Sandré-Chardonnal escreveu:
This means some file dependencies are not handled well. Maybe my .pro has
some errors that cause this?
Yes, it's possible.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source
On 24-Feb-14 17:41, Etienne Sandré-Chardonnal wrote:
I sometimes experience problems with qmake (used in QtCreator). This
happens not often, but my program crashes after a partial build, and if
I rebuild all, it works perfectly.
This means some file dependencies are not handled well. Maybe
Am 24.02.2014 um 17:49 schrieb Thiago Macieira thiago.macie...@intel.com:
Em seg 24 fev 2014, às 17:41:44, Etienne Sandré-Chardonnal escreveu:
This means some file dependencies are not handled well. Maybe my .pro has
some errors that cause this?
Yes, it's possible.
Factoring away the Usual
-Original Message-
From: interest-bounces+kai.koehne=digia@qt-project.org
files =\
foo.cpp \
foo.h \
bar.cpp \
bar.h
for(file, files) {
contains(file, '.*.h') {
message(header = $$file)
HEADERS *= $$file
}
contains(file, '.*.cpp') {
Hi, I have a question about scope tests in .pro files. The following .pro
file behaves a bit differently than I expected:
files =\
foo.cpp \
foo.h \
bar.cpp \
bar.h
for(file, files) {
contains(file, '.*.h') {
message(header = $$file)
HEADERS *= $$file
}
Em qui 13 fev 2014, às 23:10:22, Thomas Sevaldrud escreveu:
However, the problem is that all the files are added to both HEADERS and
SOURCES. It appears that the HEADERS and SOURCES assignments simply ignore
the contains()-check, even though they are placed inside the scopes of
these checks?
Wow, have to try this immediately. If this works it would be much better
than what I concocted. :-)
Guido
Hi,
actually this is possible with qmake.
If you have a file named config.h.in you can use normal qmake variables
in it e.g. #define Version $$VERSION.
Then put the following in
I wonder why such useful feature is left undocumented...
On 01/30/2014 01:27 AM, Guido Seifert wrote:
Wow, have to try this immediately. If this works it would be much better
than what I concocted. :-)
Guido
Hi,
actually this is possible with qmake.
If you have a file named config.h.in
Constantin Makshin wrote:
I wonder why such useful feature is left undocumented...
I don't know, but as with anything undocumented, handle with care.
http://thread.gmane.org/gmane.comp.lib.qt.user/10485/focus=10540
Thanks,
Steve.
___
Interest
Den 16-01-2014 14:42, Guido Seifert skrev:
Hi,
when I use cmake I can create a file config.h.in, which contains
things like:
#define Version @VERSION@
in the CMakeLists.txt I can define a variable:
SET(VERSION something)
and add:
configure_file (
config.h.in
)
This creates a
Hi, Bo.
Someday for sure. But I needed a solution fast. And a quick Python hack
was much faster than me delving into something totally unknown. Totally
unknown for me at least.
Guido
As someone already told you, no this can't be done. But instead of doing
a python script or some other home
Bo Thorsen wrote:
Den 16-01-2014 14:42, Guido Seifert skrev:
Hi,
when I use cmake I can create a file config.h.in, which contains
things like:
#define Version @VERSION@
in the CMakeLists.txt I can define a variable:
SET(VERSION something)
and add:
configure_file (
config.h.in
)
This
Hi,
when I use cmake I can create a file config.h.in, which contains
things like:
#define Version @VERSION@
in the CMakeLists.txt I can define a variable:
SET(VERSION something)
and add:
configure_file (
config.h.in
)
This creates a config.h with #define Version something.
Question is, can
On quinta-feira, 16 de janeiro de 2014 14:42:14, Guido Seifert wrote:
Question is, can I do the same with qmake? How?
system(sed )
There's a write_file function which you can use if you want to write the full
file from the .pro file.
--
Thiago Macieira - thiago.macieira (AT) intel.com
In other words: Not 'natively' with qmake.
Ok, a Python script it will be. I am a bit
more comfortable with Python than with sed. :-)
Thanks,
Guido
Question is, can I do the same with qmake? How?
system(sed )
There's a write_file function which you can use if you want to write the
There's nothing in qmake that does something like find_package - or any
other configuration.
You have to add to the LIBS, INCLUDE_PATH and DEPEND_PATH yourself.
If you want configuration, try qbs.
Bo.
en 19-11-2013 20:14, Damian Ivanov skrev:
Hi all,
I have a library (libqt-xdg) in
Thanks for your answer.
Adding External Library through qtcreator fixed my problem :)
2013/11/20 Bo Thorsen bthor...@ics.com:
There's nothing in qmake that does something like find_package - or any
other configuration.
You have to add to the LIBS, INCLUDE_PATH and DEPEND_PATH yourself.
If
Partly answering my own question.
Following lines in the pro file did the trick:
CONFIG -= embed_manifest_exe
QMAKE_LFLAGS_EXE =
Hi all,
I'm using the MS Visual C++ 10 Compiler under Windows 7 64 bit.
I'd like to build simple C console applications with qmake istead of
writing own
Good morning,
On 18 September 2013 15:48, Thiago Macieira thiago.macie...@intel.com wrote:
On quarta-feira, 18 de setembro de 2013 13:46:28, Phil Hannent wrote:
Ok, so I went digging into qt_lib_webkit.pri file and found:
QT.webkit.depends = core gui network
This one declares what your -I
Hi,
I am trying to remove some Qt modules that I don't need at the moment,
however qmake isn't outputting a Makefile with the expected syntax. In
my .pro file I have:
QT += core gui webkit
greaterThan(QT_MAJOR_VERSION, 4) {
message(Using QT5)
QT += widgets
QT += webkitwidgets
QT
Will webkit work w/o network?
I think it depends on the network module. Same might be true for other
modules, but I'm not sure.
HTH,
-mandeep
On Wed, Sep 18, 2013 at 3:19 PM, Phil Hannent p...@hannent.co.uk wrote:
Hi,
I am trying to remove some Qt modules that I don't need at the moment,
On 18 September 2013 11:28, Mandeep Sandhu mandeepsandhu@gmail.com wrote:
Will webkit work w/o network?
I think it depends on the network module. Same might be true for other
modules, but I'm not sure.
HTH,
-mandeep
On Wed, Sep 18, 2013 at 3:19 PM, Phil Hannent p...@hannent.co.uk
Hi,
I've recently downloaded Qt 5.1.0 and am attempting to build a project of
mine on a Windows 7 PC using QtCreator. The problem is that I cannot
compile the application because it cannot find the library's to link
against:
Hi all,
I have a problem with qmake setting rpath:
the sources are in
~/Software/qtwm/branches/macros/apps/apps5/app
~/Software/qtwm/branches/macros/apps/apps5/aedit
~/Software/qtwm/branches/macros/apps/apps5/lib
then the debug-build gives me the executable / lib in
On 26/04/13 16:23, Wilhelm wrote:
Hi all,
I have a problem with qmake setting rpath:
[...]
QMAKE_RPATHDIR += ../lib
by this gives me
-Wl,-rpath,/home/lmeier/Software/qtwm/branches/macros/apps/apps5/lib
in the Makefile, and that's not correct.
How do I set the rpath to point to the
Am 26.04.2013 17:14, schrieb Nikos Chantziaras:
QMAKE_LFLAGS += '-Wl,-rpath,\'\$$ORIGIN/../lib\''
Many thanks!!!
--
Wilhelm
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Thanks a lot for all your hints and links! I get the feeling that I can
easily spend a week learning the secrets of qmake. :-)
My first impression is that qmake probably will suit fine, without
introducing the complexity of cmake. But it definitely will be the
second build system (for
Nothing against qmake, but IHMO it definitely pays off to learn cmake.
Especially the cpack addition makes it worthwhile. Easy packaging for
Windows using the NSIS installer, easy deb and rpm packages for Linux,
and packages for OSX. This feature alone makes cmake far superior to
qmake.
Guido
Hi Rainer,
I suggest you to review QmkBld project:
https://code.google.com/p/qmkbld/
https://code.google.com/p/qmkbld/wiki/QmkBld
It might fulfill some of requirements.
Kind regards,
Semih Cemiloglu
semih (at) cemiloglu.org
On Fri, Apr 19, 2013 at 4:48 PM, Rainer Wiesenfarth
On Friday 19 April 2013 13:36:36 Bo Thorsen wrote:
Den 19-04-2013 12:29, Rainer Wiesenfarth skrev:
well, I know about cmake, but was going for something less cryptic... :-)
We have some fancy build stuff (f2c, versioning, ...), but I was hoping
to get it done with qmake, _because_ it is
I would like to ask for some expert tutorial or some hints for using
qmake with huge projects.
What is huge? Our complete package consists of 50 applications build
based on 100 libraries (organized in modules and units). On Windows, we
use a Visual Studio solution file containing 250
On Fri, Apr 19, 2013 at 12:18 PM, Rainer Wiesenfarth
rainer_wiesenfa...@trimble.com wrote:
I would like to ask for some expert tutorial or some hints for using
qmake with huge projects.
What is huge? Our complete package consists of 50 applications build
based on 100 libraries (organized in
Hi,
On Fri, Apr 19, 2013 at 10:35 AM, Mandeep Sandhu
mandeepsandhu@gmail.com wrote:
On Fri, Apr 19, 2013 at 12:18 PM, Rainer Wiesenfarth
rainer_wiesenfa...@trimble.com wrote:
I would like to ask for some expert tutorial or some hints for using
qmake with huge projects.
What is
Am 19.04.2013 10:35, schrieb Mandeep Sandhu:
[...]
The single application's pro file should have all the libs it depends
on, listed in the depends variable.
Thanks for your answer, I will take a look at depends - I did not yet
read in depth about its meaning and impact.
Best Regards / Mit
Am 19.04.2013 11:25, schrieb Bo Thorsen:
Sounds to me like you want to switch to cmake instead. That has a lot
better support for dependencies between subprojects than qmake. And for
a project of this size, I would expect you have some fancy build stuff
in there as well, and qmake is usually too
qmake takes care of this (I think), i.e it'll find out the number of cores
and supply the relevant number to make's -j option.
No, qmake does not take care of this as qmake is not a buildsystem itself
(rather a buildsystem generator, it generates Makefiles, VS files etc.).
But of course a
Den 19-04-2013 12:29, Rainer Wiesenfarth skrev:
Am 19.04.2013 11:25, schrieb Bo Thorsen:
Sounds to me like you want to switch to cmake instead. That has a lot
better support for dependencies between subprojects than qmake. And for
a project of this size, I would expect you have some fancy
Den 19-04-2013 13:36, Jan Kundrát skrev:
On Friday, 19 April 2013 12:29:04 CEST, Rainer Wiesenfarth wrote:
well, I know about cmake, but was going for something less cryptic... :-)
One of my biggest disappointments with qmake was that it just did not set up
proper dependencies between the
Am 19.04.2013 13:36, schrieb Bo Thorsen:
On the bright side: Once you have a good cmake build in place, you will
have the visual studio build done with the same system as Linux. Having
two different build systems is *not* a good idea.
I know, but we will definitely have two build systems -
Hi Rainer,
as other members already stated out qmake has some limits - but:
These can be hacked ;-)
We (our company) spent much time to discover different build systems and
approaches -
where CMake was the most complicated and most work intensive solution.
So we decided to use the long term and
: interest@qt-project.org
Sent: Friday, April 19, 2013 8:33 AM
Subject: Re: [Interest] qmake: questions regarding huge projects
Am 19.04.2013 13:36, schrieb Bo Thorsen:
On the bright side: Once you have a good cmake build in place, you will
have the visual studio build done with the same system
Now, I do it. I can edit the qt.conf file located in qmake.exe directory
with
[Paths]
Prefix=c:/qt-sdk/
On 03/15/2013 10:34 AM, tang ke wrote:
Thanks very much.
but I found the system registry, I find that the
HKEY_CURRENT_USER\Software\Trolltech\OrganizationDefaults andr QMake.
when I
hi everybody!
Now I download the qt-opensource-mingw32-4.8.2.zip from the web. and
install it.
but after I use the qmake -unset QT_VERSION commands, then I use qmake
-query, It can display the QT_VERSION .
who can tell me where the qmake -set prop value is stored with windows?
thanks in
On sexta-feira, 15 de março de 2013 10.06.46, tang ke wrote:
hi everybody!
Now I download the qt-opensource-mingw32-4.8.2.zip from the web. and
install it.
but after I use the qmake -unset QT_VERSION commands, then I use qmake
-query, It can display the QT_VERSION .
who can tell me where
Hi,
I have the following problem.
I have a lib let's call it libA in /usr/lib64 and /usr/local/lib the only
difference is the Version of libA (the one in /usr/local/lib is newer).
If I now create a simple qmake project it generates a Makefile with the line:
LIBS = $(SUBLIBS)
Hi,
I for now solved he problem with a quiet dirty workaround.
I added the line
QMAKE_LIBDIR_FLAGS = -L/usr/local/lib
to my pro file, which in turn results in the Makefiles line:
LIBS = $(SUBLIBS) -L/usr/local/lib -L/usr/lib64 -L/usr/local/lib -
lQtGui -lQtCore -lpthread
which is not
On quarta-feira, 28 de novembro de 2012 14.57.22, Alexander Görtz wrote:
I for now solved he problem with a quiet dirty workaround.
I added the line
QMAKE_LIBDIR_FLAGS = -L/usr/local/lib
to my pro file, which in turn results in the Makefiles line:
LIBS = $(SUBLIBS) -L/usr/local/lib
On 28/11/12 23:33, Alexander Görtz wrote:
My question is if there is any possibility to tell qmake not to add the -
L/usr/lib to the makefile or if this is not possible to add -L/usr/local/lib
even before that.
You could do LIBS += /usr/local/lib/libmylib.so instead of -lmylib to
explicitly
I'm updating compilers on my virtual machines and just installed VS2012, namely
to test to see what needs to be done to support it for my main projects - all
Qt based. I have a number of compilers around - from VS6 to VS2010, and want to
see if VS2012 is useful enough to add support for.
Any
Hi,
Is it possible to say in QMake projects that when changes appears in the
library then all targets, depended on that library, must rebuilded?
Because at this time I see that when I change something in the library
then recompilation occur only on that library, and all targets that
links to
Hi,
Have a look at:
http://qt-project.org/doc/qt-4.8/qmake-variable-reference.html#pre-targetdeps
Hope it helps
Thanks. It helps.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Hi there,
I would like to build a shared object (PySide module) using qmake.
My first attempt was to use TEMPLATE=lib, which worked except that I
have no control on the name of the output file.
Is there a way to override the name of the generated shared object file?
Basically using
Hi,
Am Mittwoch, 27. Juni 2012 schrieb Christian Gagneraud :
On 27/06/12 12:32, Mandeep Sandhu wrote:
On Wed, Jun 27, 2012 at 4:29 PM, Christian Gagneraud
ch...@techworks.iejavascript:;
wrote:
Hi there,
[...]
If you build a plugin, then the version links are not created, and
On 27/06/12 18:26, Andreas Pakulat wrote:
Hi,
Am Mittwoch, 27. Juni 2012 schrieb Christian Gagneraud :
On 27/06/12 12:32, Mandeep Sandhu wrote:
On Wed, Jun 27, 2012 at 4:29 PM, Christian Gagneraud
ch...@techworks.ie javascript:; wrote:
Hi there,
[...]
The title says it all. With Qt 4.7.x and Visual C++ 2008 one used to
be able to generate a Visual Studio project file by running 'qmake
-spec win32-msvc2008' from the Qt command window.
Now with Qt 4.8.1 and Visual C++ 2010, running 'qmake -spec
win32-msvc2010' only generates Makefile,
On quinta-feira, 29 de março de 2012 13.59.00, Sherif Ghali wrote:
The title says it all. With Qt 4.7.x and Visual C++ 2008 one used to
be able to generate a Visual Studio project file by running 'qmake
-spec win32-msvc2008' from the Qt command window.
You need to add: -tp vc
--
Thiago
Hi Sherif,
Generated makefiles for nmake or generated vcproj for visual studio,
depending on which TEMPLATE you used in your .pro file.
app / lib == makefiles
vcapp / vclib == .vcproj
As Thiago said, the convenient way to do this is add -tp vc to
qmake's command line, if you TEMPLATE is app or
To: interest@qt-project.org
Subject: Re: [Interest] qmake Conditions and Scopes
On 03/12/2012 02:33 PM, ext Szalata, Zenon M. wrote:
I took this from qmake Advanced Usage available in assistant.
It's terribly limiting to make decisions based on the mkspec and almost
always wrong (even when Qt
I am trying to implement a project file to build my project conditionally. In
my case the condition is the host architecture, either 32 bit linux or 64 bit
linux. I tried something like this:
message($$QMAKESPEC)
linux-g++-32 {
message( have 32 bit linux)
}
linux-g++-64 {
message(have 64
On 03/12/2012 02:33 PM, ext Szalata, Zenon M. wrote:
I took this from qmake Advanced Usage available in assistant.
It's terribly limiting to make decisions based on the mkspec and almost
always wrong (even when Qt does it). We've turned up bugs by failing to
name custom mkspecs in precisely
Hi,
I'm wondering what would be the recommended way to pre-process QML?
# Add more folders to ship with the application, here
folder_01.source = qml/n9test
folder_01.target = qml
DEPLOYMENTFOLDERS = folder_01
At deployment time I'd like to change the QML, but keep the unchanged copy
in version
13.02.2012, 18:19, Harri Pasanen ha...@mpaja.com:
Hi,
I'm wondering what would be the recommended way to pre-process QML?
# Add more folders to ship with the application, here
folder_01.source = qml/n9test
folder_01.target = qml
DEPLOYMENTFOLDERS = folder_01
At deployment time I'd like
101 - 200 of 200 matches
Mail list logo
