[Interest] Well, I'm kind of irritated by QtCreator...
I'm trying to work on a subproject of a larger application, and I am kind of
irritated by QtCreator's inability to handle invalid command line characters.
I cannot change the folder names I must reference for things like headers and
link libraries, and those paths contain parentheses. QtCreator is choking on
these characters:
g++ -c -pipe -g -std=c++0x -Wall -W -D_REENTRANT -fPIC -DQT_NETWORK_LIB
-DQT_CORE_LIB -I../Mediator -I. -I../Source\ (Shared)/Processing/ ...
/bin/sh: 1: Syntax error: "(" unexpected
make: *** [main.o] Error 2
10:56:44: The process "/usr/bin/make" exited with code 2.
I cannot change the names of these paths I must reference, nor can I ask them
to change the folder names to suite my chosen IDE. I can escape the paths
when I am referencing them explicitly (e.g., "../Source
\\(Shared\\)/Processing/..." seems to work), but when I have to use something
like $$PWD, everything breaks because the characters are not properly escaped.
Any tricks I can apply to overcome this? Otherwise, can somebody point me to
the location in QtCreator where these command-line fix-ups are performed? I
guess I'll have to divert some time to see if I can apply corrections if I
want to keep using this IDE.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Well, I'm kind of irritated by QtCreator...
Il 20/10/2015 19:52, Bob Hood ha scritto: I cannot change the names of these paths I must reference, nor can I ask them to change the folder names to suite my chosen IDE. I can escape the paths when I am referencing them explicitly (e.g., "../Source \\(Shared\\)/Processing/..." seems to work), but when I have to use something like $$PWD, everything breaks because the characters are not properly escaped. See qmake's $$system_quote, $$shell_quote and the like (depends on what you're doing exactly). Any tricks I can apply to overcome this? Otherwise, can somebody point me to the location in QtCreator where these command-line fix-ups are performed? I guess I'll have to divert some time to see if I can apply corrections if I want to keep using this IDE. Why do you think it's Creator's fault? You seem to have identified the problem in your usage of qmake (lack of escape for paths). Creator just runs qmake + make, which then explodes; it doesn't look to me Creator is to blame. HTH, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Software Engineer KDAB (UK) Ltd., a KDAB Group company | Tel: UK +44-1625-809908 KDAB - The Qt Experts smime.p7s Description: Firma crittografica S/MIME ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Well, I'm kind of irritated by QtCreator...
On Tuesday 20 October 2015 11:52:55 Bob Hood wrote:
> I'm trying to work on a subproject of a larger application, and I am kind of
> irritated by QtCreator's inability to handle invalid command line
> characters. I cannot change the folder names I must reference for things
> like headers and link libraries, and those paths contain parentheses.
> QtCreator is choking on these characters:
First of all, that's not a Qt Creator problem. Qt Creator just runs make. You
need to blame your buildsystem.
I assume you're using qmake, correct?
> g++ -c -pipe -g -std=c++0x -Wall -W -D_REENTRANT -fPIC -DQT_NETWORK_LIB
> -DQT_CORE_LIB -I../Mediator -I. -I../Source\ (Shared)/Processing/ ...
> /bin/sh: 1: Syntax error: "(" unexpected
> make: *** [main.o] Error 2
> 10:56:44: The process "/usr/bin/make" exited with code 2.
>
> I cannot change the names of these paths I must reference, nor can I ask
> them to change the folder names to suite my chosen IDE.
Your IDE has nothing to do with this.
> I can escape the
> paths when I am referencing them explicitly (e.g., "../Source
> \\(Shared\\)/Processing/..." seems to work), but when I have to use
> something like $$PWD, everything breaks because the characters are not
> properly escaped.
>
> Any tricks I can apply to overcome this?
Use another tool besides qmake. For example, cmake.
You said you can't change the names. Does that mean the buildsystem existed
before you started using Creator? If so, did it work? That is, if you opened a
terminal and tried to compile, did it succeed? What buildsystem is that?
And what did you do when to open that project in Qt Creator?
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Well, I'm kind of irritated by QtCreator...
On Tuesday 20 October 2015 13:37:47 Bob Hood wrote: > > Use another tool besides qmake. For example, cmake. > > So, qmake is the likely culprit here? > > > You said you can't change the names. Does that mean the buildsystem > > existed > > before you started using Creator? If so, did it work? That is, if you > > opened a terminal and tried to compile, did it succeed? What buildsystem > > is that? > This source base is Windows; I am not building it at all. I am porting some > elements of it to Linux, and so have to make references (to thing like > headers in an exposed SDK). So you're creating a buildsystem that refers to files that you can't move around. Try the functions that peppe suggested. Otherwise, use cmake. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Well, I'm kind of irritated by QtCreator...
On 10/20/2015 12:08 PM, Thiago Macieira wrote:
> On Tuesday 20 October 2015 11:52:55 Bob Hood wrote:
>> I'm trying to work on a subproject of a larger application, and I am kind of
>> irritated by QtCreator's inability to handle invalid command line
>> characters. I cannot change the folder names I must reference for things
>> like headers and link libraries, and those paths contain parentheses.
>> QtCreator is choking on these characters:
> First of all, that's not a Qt Creator problem. Qt Creator just runs make. You
> need to blame your buildsystem.
>
> I assume you're using qmake, correct?
I'm simply opening the *.pro file in QtCreator. I assume it's using qmake
somewhere in that chain.
>> g++ -c -pipe -g -std=c++0x -Wall -W -D_REENTRANT -fPIC -DQT_NETWORK_LIB
>> -DQT_CORE_LIB -I../Mediator -I. -I../Source\ (Shared)/Processing/ ...
>> /bin/sh: 1: Syntax error: "(" unexpected
>> make: *** [main.o] Error 2
>> 10:56:44: The process "/usr/bin/make" exited with code 2.
>>
>> I cannot change the names of these paths I must reference, nor can I ask
>> them to change the folder names to suite my chosen IDE.
> Your IDE has nothing to do with this.
Good. I didn't want to hack on Creator anyway. :)
>> I can escape the
>> paths when I am referencing them explicitly (e.g., "../Source
>> \\(Shared\\)/Processing/..." seems to work), but when I have to use
>> something like $$PWD, everything breaks because the characters are not
>> properly escaped.
>>
>> Any tricks I can apply to overcome this?
> Use another tool besides qmake. For example, cmake.
So, qmake is the likely culprit here?
> You said you can't change the names. Does that mean the buildsystem existed
> before you started using Creator? If so, did it work? That is, if you opened a
> terminal and tried to compile, did it succeed? What buildsystem is that?
This source base is Windows; I am not building it at all. I am porting some
elements of it to Linux, and so have to make references (to thing like headers
in an exposed SDK).
> And what did you do when to open that project in Qt Creator?
As I said, I opened my *.pro file directly. Nothing acrobatic. My portion of
the project is pure Qt/Linux.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
