Qt Creator and other tools

The problem was solved. Last modified some files were later than today.

Thanks.
Using a file is where I started but I still have to know where the file is. My hope was to have a small line in each of my project files that determined the location of the specific file.

Although I would love to know why Qt3 runs in fine and Qt4 qmake does not.

I figured out a qmake project file version that seems to work.

@
rules_dir=$$IN_PWD
pwd=$$split(IN_PWD,/)
for(p,pwd){
exists($$rules_dir/rules.make):eval(RULES_DIR=$$rules_dir):break()
else:rules_dir=$$dirname(rules_dir)
}
@

[EDIT: code formatting, please wrap in @-tags, Volker]

First reply edited :) sorry.

Setting include paths is usually handled with the C/C++ flags. In qmake projects you add

@
INCLUDEPATH += $${appBaseDir}
@

I suppose you created a qmake project with a .pro file.

In that case you need to adjust the LIBS variable, the qmake documentation has the details in the "declaring other libraries":http://developer.qt.nokia.com/doc/qt-4.7/qmake-project-files.html section. You will need to add all the libs that your have added in the XCode project too.

Yep on my previous work we using CruiseControl, It is good system. Here you can find our fork with improvements for Qt and Git (sic! we didn't test it with svn): https://github.com/dkormalev/cruisecontrol.rb

[quote author="peppe" date="1317714974"]You don't have to reconfigure Qt. OpenSSL is already enabled. If you want to recompile Qt (for instance, to statically link openssl into it) then you have to grab the sources and compile from scratch (do NOT use the sources inside the sdk).[/quote]

Is openssl enabled ? Can i use blowfish for encryption so ?

In docs - http://doc.qt.nokia.com/4.7-snapshot/configure-options.html
openssl - Compile in run-time OpenSSL support - This option denotes a default value and needs to be evaluated. If the evaluation succeeds, the feature is included.

I need openssl cyrpto library. I need encrypt a file with qt app and decrypt with php server app. So openssl is standart for this process.

Thanks for answers.

I also checked that flicking isn't enable with:
@
...
dw = new QDeclarativeView(QString("qrc:myqml.qml"), this);
QGridLayout *gl = new QGridLayout(ui->declarativeBaseWidget);
gl->addWidget(dw);
...
@
where ui->declarativeBaseWidget is a QWidget added from QtCreator...

[quote author="Tobias Hunger" date="1317491134"]Did you "file a bug report":http://bugreports.qt.nokia.com/?[/quote]

I just reported the "bug":https://bugreports.qt.nokia.com/browse/QTSDK-954 .

This is my first bug report so I hope have been clear... :-)

Ok, ALT + Left do the works! :-)

I found it: Project->Build->Qt Version

hi , it is clear that VS2008 cannot find the .h ( headers ) of your project , so you should spicify the location of each one or make them in the same folder that containe the .c/.c++ files .it will work :)

Thanks a lot. And it looks like a good idea to have completion as case sensitive. For the problem occurs mostly with m$ code and since most of its shouting aloud anyway(I mean most of it is in CAPS), it leads to fewer troubles.

i have used the programcentral in debian to install qt and all libs to qwt and other plugins.
None of the plugins will work when i build the projects

i'm very newbie on both Debian and qt
i can't even build and run the qt exampels
something must be very wrong in my system.

I used also a small perl script to apply a license file at the beginning of each project file if I forgot to do from the beginning of the project.

[quote author="Lukas Geyer" date="1317063129"]As a workaround right-click (or shift right-click if you are on Windows Vista+) your window in the taskbar and select 'Move'. You then can move your window using the arrow keys - even beyond screen boundaries.[/quote]

I know, but it makes you able only to see the bottom part of the settings dialog, not interact with it.
Looking forward to Qt Creator 2.4.0.

One possibility would be "QMAKE_EXTRA_TARGETS":http://doc.qt.nokia.com/latest/qmake-environment-reference.html#customizing.

That sounds like a bug to me. Have you tried "reporting it":http://bugreports.qt.nokia.com/?