February 11, 2012

Viderizer Viderizer
Lab Rat
13 posts

Problems building after build interrupt

 

So, after all the instructions I got, I was building Qt fom the sources, but then the computer’s plug slipped off and now when I try to compile again, it gives me “nmake” was not recogniced as a command. I tried downloading the source again and doing everything from the start, I started configure, it gave me:

Creating qmake…
execute: File or path is not found <nmake>
execute: File or path is not found <nmake>
Cleaning qmake failed, return code -1.

I’m compiling with Visual Studio 2010 in Windows

 Signature 

Thank you for wasting your time reading this signature.

10 replies

February 11, 2012

koahnig koahnig
Dinosaur Breeder
2907 posts

Did you remember to start the compilation from vc command prompt?

February 11, 2012

Viderizer Viderizer
Lab Rat
13 posts

Yea.

 Signature 

Thank you for wasting your time reading this signature.

February 11, 2012

koahnig koahnig
Dinosaur Breeder
2907 posts

Hmpf…
I guess you have tested also that nmake can be found from that prompt?
When it is still available, it is probably the best to start with a clean configuration of Qt.

February 11, 2012

Viderizer Viderizer
Lab Rat
13 posts

Creating qmake…
execute: File or path is not found <nmake>
execute: File or path is not found <nmake>
Cleaning qmake failed, return code -1.

It’s giving me that when I try to configure

Also, nmake worked before the interrupt, now it sais the command doesn’t exist, could this be a problem with VS2010 then?

 Signature 

Thank you for wasting your time reading this signature.

February 11, 2012

koahnig koahnig
Dinosaur Breeder
2907 posts

Ok, did not read careful enough your first post :-(

Viderizer wrote:

Also, nmake worked before the interrupt, now it sais the command doesn’t exist, could this be a problem with VS2010 then?

This was my other suspicion. That is the reason for asking this:
koahnig wrote:

I guess you have tested also that nmake can be found from that prompt?

Please test if nmake can be called in the vc tools command prompt.

February 11, 2012

Viderizer Viderizer
Lab Rat
13 posts

I don’t understand what you are asking :( , but everythime I try to call nmake, it just returns The command “nmake” wasn’t recogniced… Also I just noticed the prompt gives this message when started, I didn’t see it before the interrupt, “ERROR: Cannot determine the location of the US Common Tools folder”.

By the way, I just tried repairing VS2010 and when restarted computer like it asked, it gave me some error from another installer and didn’t finish :/

 Signature 

Thank you for wasting your time reading this signature.

February 11, 2012

koahnig koahnig
Dinosaur Breeder
2907 posts

So, it looks like your vc installation is broken.
I was asking to start nmake from command prompt in vc in order to see, if this might be the problem. And as it looks, it is the problem.

You need to create a complete installation of msvc again. Since repairing did not work out, you better remove it completely and reinstall freshly including all service packages.

Let’s the fingers crossed that nothing in addition is broken in your installation.

February 11, 2012

Viderizer Viderizer
Lab Rat
13 posts

Hmm, any advice on totally uninstalling VC? There are multiple parts it has intalled and it owuld take a lot of time to remove them on-by-one

 Signature 

Thank you for wasting your time reading this signature.

February 11, 2012

koahnig koahnig
Dinosaur Breeder
2907 posts

Well, I understand you hesitation though. No experience with vc 2010 since I have msvc 2005. But this takes some time.
You need to get it repaired. If this is possible without complete deinstallation you may have to check a msvc forum, or to be a bit patient in this forum. But the number of msvc 2010 users seems to be limited in the forum.

February 11, 2012

Viderizer Viderizer
Lab Rat
13 posts

This is weird. I downloaded a deinstaller tool from microsift site, and then reinstalled and it’s still saying that o.O

EDIT: Googled a bit and found a stackoverflow page where someone said that some path in the PATH env variable had upset a VS bat file, I removed everything unneeded, and added sys32 as someone else instructed and now it is working! Thanks for your help :)

 Signature 

Thank you for wasting your time reading this signature.

 
  ‹‹ dyld: Library not loaded:      Qt not passing details to Visual Studio linker to generate .manifest file ››

You must log in to post a reply. Not a member yet? Register here!