Up until a couple hours ago pressing CTRL+R while in Qt would build and run my code. However something changed that I am unaware of that doesn't commit the changes that I make to the GUI. If I move a button for example then rebuild and run, the application will display its previous location. Something to note however, if I run "qmake && make" in a terminal, then rebuild from the GUI it will work. It's a bit of a hassle to keep doing that and thus a solution would be appreciated.
I'm using Qt5 in a Debian 7.0 based environment
Update: I had to disable shadow build to get it to build properly, but I cannot build in another directory
Related
I have downloaded angular 2 application from this link:
https://github.com/aravindfz/firstAngular2App
How to run this application?
Which angular cli version install to run angular 2 application?
I tried from some questions stackoverflow but not working properly.guys this question is not duplicate..Please understand.
Anyone can give clear details?
I need step by step procedure.
If you cloned the repo and did nothing else, there are a few things you need to do before you can run the app. Since I don't know how much web development you have done, I'm going to include things some people will think unnecessary.
Install node.js, if you haven't yet. Grab the LTS release from https://nodejs.org/en/. Do not use the "Current" version, because that may not be compatible with Angular just yet. If you have and older version of Node, upgrade. If you already have the LTS version, skip this step.
Now open a new command prompt or terminal and change to the directory where you cloned the repo. To be sure you're in the right place, make sure you can see a file named package.json.
In this command prompt/terminal window, execute this command: npm install. This will download and install all the dependencies (which could rather disturbingly add up to a few hundred Megabytes). You may experience timeout errors if you're behind a corporate proxy server. That's not something you can fix as of 2018. Just connect using something else and try again.
Once everything is installed, you should be able to run the Angular app. Everything I mentioned already only need to be done before you run it the first time. To ensure you are in the right folder, navigate to where your index.html is located and run this command: ng serve. If ng cannot be found, you may need to install it. To do so, execute npm install --save-dev #angular/cli. Now it should work. If not, close your command prompt/terminal window, open a new one and try ng serve again.
Once ng serve is finished compiling, you should be able to view your app by opening http://localhost:4200 in your favourite browser.
And that's it!
Here's a bonus tip: Take the time to work through the official Angular Quick Start. It really is a fantastic guide and will get you skilled up much quicker than just hacking it ever will.
Good luck.
Does it make a difference (and if so, what difference) where I add the make install step?
In some posts they say to add it under Build like in the first screenshot. Others say it needs to go under Run/Deployment like in the 2nd.
Are both ways equivalent?
If it is part of Build Settings, it will be done every time you do a build under Qt Creator (assuming previous steps succeeded).
If it is part of Run Settings, it will only be run when you actually run the app under Qt Creator.
It depends on the case, which on you want. If it is part of Run Settings, then logically it should be configured to run the installed/deployed binary. If it is just for checking that make install succeeds, as part of the build, even though it will run the application from build directory when you run it under Qt Creator, then it should be part of build.
In your case, it sounds like make install is needed for running the app, so maybe it could be part of Run settings, to make normal builds just a bit faster.
I am using Qt 5.10.1 on windows 10, when I was trying to add qt repositories using the Maintenance Tool, specifically I need to add the Qt Charts module. Then it gave me this error:
Your Maintenance Tool appears to be older than 3.0.2. Please update it first to get access to new Qt packages.
Why would this happen? I am currently using the latest Qt version, and I did not find a way to update the Maintenance Tool. How can I solve this problem?
I just encountered this issue.
Strangely enough, if you hit the quit button when this happens, the tool moves onto the next page, and then prompts you if you want to exit. If you cancel exiting, it then allows you to update the maintenance tool (the current version is apparently 3.0.4).
So basically, hit "quit", cancel the exiting, and it then updates itself.
I'm trying to make an installer using the Qt Installer framework and when an upgrade is available in the software (checked through our rest API), our software will download the new installer and run it.
This should of course uninstall the previous version first, however, it seems just running it will give you "The folder you selected already exists..." error.
I thought using the maintenance tool that is generated would provide a solution, however, it seems that there is no way to run this with a switch to just do the uninstall. It shows up with the dialogue of uninstall, upgrade... which would confuse the users.
Is there a way to get the maintenance tool or otherwise to uninstall the program, so the update can be run?
EDIT:
If this cannot be done, can anyone suggest a good cross platform installer framework?
Do not try to run the installer again, run the maintenancetool.exe to update. You can make a "silent" update by passing a script to the maintenance tool like this:
#echo off
maintenancetool.exe --checkupdates > checkUpdate.txt
findstr /c:"updates" checkUpdate.txt
if %errorlevel% == 0 maintenancetool.exe --script=script.qs
http://doc.qt.io/qtinstallerframework/noninteractive.html
I've just downloaded Aptana to do some web-development. I've downloaded the JsTestDriver plugin (javascript testing framework) which works fantastic, however there is one thing bugging me... In my run configuration of JsTestDriver i set it to run everytime i save my project. The funny thing is that the my run configuration is executed everytime i press a key... Does this mean that aptana saves my project everytime i make a single change to it? If so, how do I disable it? Running all my unit tests everytime i press a single key is kinda taxing on my system :P
Found it! Disable "Build Automatically" in Eclipse -> Workspace settings