Failed to start program. Path or permissions wrong?
-
[quote author="clouca" date="1367907957"]john_god john_god i didn't found something simillar
my project was created in qt 4.7 32(bit) and i am now running Qt 5.0 (64bit) if that can help..
thanks[/quote]
Those are the versions of Qt lib. Qt creator has currently version 2.7. A Qt creator installed with Qt 4.7 is fairly old.
How did you install Qt 5? Which exact Qt5 version are you using? Did you replace also the Qt creator at that time? -
Where does that path come from ?
-
Do you set the DESTDIR in your pro files ? If yes where do they point to ?
Otherwise can you post (i.e. pastebin) your pro files ? So we can see if the problem lies with them or if we can eliminate that as a cause.
Did you take a look at the build panel to see where things are built ?
-
As I said before, without seeing anything from your project I can only make guesses.
If you really can't share anything. The only solution I see for you is to start from scratch a new project using the subdir template with only one sub directory that contains a project for a hello world app. Make it build and run and once that is good. Take one by one the pieces of your other project and integrate it in the one building and running until everything works.
-
As already mentioned, seeing the pro files could be useful
-
I've run today into same problem.
It appears a bit weird.When this error occurs, the exe has the Windows' typical blue/yellow shield over the icon.
Interestingly, this can be changed only by changing the name of the executable in the .pro file(TARGET=).As a first assumption I would say: If it contains the name of one of the parent directories this problem pops-up.
I run QtCreator 2.4.1on Win7.
Any comment on this?
-
Did you stop your application before rebuilding ?
-
yes.
Actually, I've did rebuilds after each name change.
First I tought about 8 char name, but was not the case.
My structure is something like:
@E:\Develop
projects
Proj1
Proj2
Proj3
AstDistpatch
source
build-Debug
build-Release
Proj5
@When I used 'AstDispatch' or 'Ast-Dispatch' or 'AstDispatchX' the executable was marked with the shield.
If I named it AstDispatceh' it was ok. -
That shield is typically associated with User Access Control. As a test I would turn off UAC and see if your default .exe name works. Alternately (as a test only) you could try going to the properties and the security tab and see if Run as Administrator is checked. This won't be a fix though because I would suspect that if you check or uncheck it, it will go back to what it was when you rebuild. I once had a similar intermittent problem with Visual Studio. I believe my fix was to disable indexing on my development folder.
-
I understand the meaning of the shield.
My question is not what the shield means, but why this is related to the name of the file.I don't want to remove the effect, but understand the cause.
Is this related to OS - Win7 decides this is a vulnerable exe based on the name? or to compiling - Qt marks the file differently?in poor wording: the shield causes that the OS asks you if you would like to run this unsigned exe. When started from the designer it causes to fail due security reasons.
-
Windows is automatically marking some files based on their names (especially if they contain something like "setup" or "install").
