problem: make: *** Waiting for unfinished jobs....

Go To Last Post
115 posts / 0 new

Pages

Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi everyone!
I have a proble with avr studio 5.1 . When i build solution a project, avrstudio don't execute with message:

    Invoking: AVR/GNU C Compiler make: *** Access is denied.
    . Stop.
    make: *** Waiting for unfinished jobs....
Any one know the solution?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

un/reinstall

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Now I have same problem, and I am using AS6 (version 6.0.1882) on windows 7, and run as administrator.

each time, "make" maybe stops at different file.

Do you guys have any solutions?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I am using AS6 (version 6.0.1882)
Just in case it does help you may want to install SP1 which takes you to "6.0.1938 Service pack 1"

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Atmel installs data files in a highly protected area. Namely "Program Files (x86)". This might somehow be causing your problem. Hopefully there is an option to install it somewhere else. I would consider that the next time I install. One of the things I would suspect is your anti-virus. You might try a quick test by temporarily disabling the anti-virus while doing a build.

It's interesting that the errors mention "make". Apparently Atmel Studio constructs a makefile and then runs make. Maybe there is something wrong with the make program. Maybe Atmel Studio is finding another make program you have laying around.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I also use AS6 (6.0.1882) on windows 7. I installed in the default directory, and the Microsoft Security Essentials antivirus is running.

No problems so far.

Sid

Life... is a state of mind

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I am running AS6/SP1 on Windows 7 as administrator. I intermittently have this issue. I haven't looked into the problem, but hitting the cancel button (to right of build button) followed by a clean then a build seems to work.

Gamu The Killer Narwhal
Portland, OR, US
_________________
Atmel Studio 6.2
Windows 8.1 Pro
Xplained boards mostly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You may have to tick /View/Toolbars/Build to see the Cancel button.

For some reason, they didn't include that command in the Build menu so the toolbar is the only option unless you add it to the menu yourself.

Ctrl+Break should work as well.

Sid

Life... is a state of mind

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It is a freeRTOS project. Maybe it is because there are too many files in project. It won't happen if it is a standalone project.

There is one way to solve it. press "cancle build" when get this error, and then build again (do not clean project. it will start compile from last stop position). I also set "32" in build and run option.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

make: *** Waiting for unfinished jobs....

Go to sysinternals.com and get procexp.exe then use that to observe what's running when you get this message. AS6 simply spawns a command prompt session to run make then asynchronously awaits completion. Similarly make spawns the compiler/linker and awaits completion. The message "waiting for unfinished jobs" would appear to suggest that something is still running in the background.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It seems that some program can't access some file.

Quote:
Invoking: AVR/GNU C Compiler
make: *** Access is denied.
. Stop.

When I fix up the iox....h files, I have a hard time getting access. I'm surprised that any builds work, but they do.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

nvhop2010 wrote:
Hi everyone!
I have a problem with avr studio 5.1 . When i build solution a project, avrstudio don't execute with message:
    Invoking: AVR/GNU C Compiler make: *** Access is denied.
    . Stop.
    make: *** Waiting for unfinished jobs....
Any one know the solution?

I have exactly the same problem with rev 6.0.1996 (SP2) while building a project with about 30 source files. The file at which it says "make: *** Access is denied." is random, suggesting that it's a timing problem.
Does anyone have a fix?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I've noticed it a couple times. For some reason, files in the \bin folder are getting set to read only. Change them back to R/W with windoze exploder and the compiler will begin functioning normally again.

Oh yes. Studio 5 was a bad nightmare. Get rid of it and install 6.

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Torby wrote:
I've noticed it a couple times. For some reason, files in the \bin folder are getting set to read only.

I looked at the user permissions of the files in the make folder, they were all RWE, as to be expected.
Submitted an error report to Atmel, it's ticket 708246

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have been getting the same a few times today.

I simply deleted everything in the Default folder of the project, including the Makefile, did a "Clean solution" and rebuilt the project.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have not seen this problem in AS6. However, yesterday I saw it in VS2010. In there, /Build/Cancel stopped the build but that didn't help subsequent builds - a file was locked, preventing the toolchain from updating it...

Sid

Life... is a state of mind

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Just to note that a useful tool when trying to diagnose this kind of thing is process explorer (procexp.exe) from www.sysinternals.com. It will show you what files a process has locked that can help. You can also use the Find menu to find which process has a file locked.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
Just to note that a useful tool when trying to diagnose this kind of thing is process explorer (procexp.exe) from www.sysinternals.com. It will show you what files a process has locked that can help. You can also use the Find menu to find which process has a file locked.
I got a quick response to the ticket, asking for further information, including the procexp.exe findings.
While investigating the problem I found a probable fix. Clean the solution, rename the file Makefile and rebuild the solution. Afterwards I couldn't reproduce the problem any more.
Thanks to clawson and Atmel support for the quick responses

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Clean the solution, rename the file Makefile and rebuild the solution
Pretty much what I said above. :-)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

One of my friend Jobin, suggested this. seems like a typical anti virus fix. Can give it a try ... https://groups.google.com/forum/...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I still see this:

Somehow, whenever I start a NEW project, there's a readonly .elf file. Once I set it to R/W, it makes fine. I made 3 tiny programs the other day.

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Can you try building project from command line ?

Project_configuration_directory>> make all

We can isolate the issue Make/Studio?

:D

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Barely used the command line since DOS days. Well, maybe CP/M days.

Can you give me a pointer HOW to build a project from command line?

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

Can you give me a pointer HOW to build a project from command line?

He did:
Quote:
Project_configuration_directory>> make all

E.g.

C:\Yourname\Documents\Atmel Studio\Yoursolution\Yourproject\Debug> make all

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The few times I have had that problem appear I only had to "cancel" the build, "clean" the project and the next time it works.

The first time I did more work than seem necessary.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Oh. You mean like this!

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Back to the future by 25 years!.. :?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

There should be a make program here:
C:\Program Files (x86)\Atmel\Atmel Studio 6.0\make\make.exe

The question is "what will you do with that?". Maybe the easiest solution is to use Windows Explorer to make a copy of that make.exe and put it in the folder where the makefile is.

It might be a good idea after you are done with it, to move it or delete it. The reason is the unlikely chance that Atmel will change their make.exe through an update and unbeknownst ( is that a real word?) to anyone, you will still be using the old one.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

Back to the future by 25 years!

Rubbish. There are still several good uses for command prompts, just like there are for GUIs.

Quote:
Oh. You mean like this!

I tested my advice on my system, but I of-course have WinAVR also and WinAVR adds it executable directories to the PATH. Atmel Studio does not.

So CMD needs to know where to look for make.exe. For repeated uses, I would recommend adding the directory to the PATH variable (And I strongly recommend against steve17s advice on copying the executable!). For a one time test you could simply give the compete path on a command line:

C:\Yourname\Documents\Atmel Studio\Yoursolution\Yourproject\Debug> "C:\Program Files (x86)\Atmel\Atmel Studio 6.0\make\make.exe" all

Verify the actual path since it varies with e.g. 32/64-bit systems.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

hehe

With the full path to make.exe, it now says "Nothing to be done for 'all'."

Odd that something keeps setting the debug folder, or sometimes a file within to read only. Haven't seen it with Visual Studio yet, but then, I don't use VS very often.

Attachment(s): 

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You are almost there, just you need to add clean command, it will delete all the previously generated files. It is equivalent to rebuild.

>>make clean all

:D

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ok. Now I've succeeded in doing a make from the command line. What were we hoping to find out by doing this again?

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
What were we hoping to find out by doing this again?

I've re-read the thread for you :wink:
mailtosarathy wrote:
Can you try building project from command line ?
[..]
We can isolate the issue Make/Studio?

So, it seems we are down to a matter of how Studio runs GNU Make - a problem with GNU Make itself is ruled out. I guess you'll have to wait until mailtosarathy returns to see what he thinks of this.

Apart from that, you now have a workaround.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Poor Thorby, do your fingers hurt after typing such a long command? :mrgreen:

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks Torby,
Just to make sure, did you try to build several time from the command line ? (as said earlier in the thread the issue is not consistent)

If there are no issue with GNU Make then there could be issue in the synchronization with Atmel Studio. My guess is in the solution explorer where Output File, Dependency information is populated.
Created internal bug for this (AVRSV-4347).

:D

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

js wrote:
Poor Thorby, do your fingers hurt after typing such a long command? :mrgreen:
No need to do much typing. I avoid that at all costs.

If you don't want to put make.exe in the current folder, you can use a batch file. A batch file is a simple text file that contains one or more commands. The name of the file must have the .bat file name extension.

You can create a file called something like make.bat and put something like this in it.

"C:\Program Files (x86)\Atmel\Atmel Studio 6.0"\make\make.exe all

Then just type make.bat
The quotes are necessary because cmd shell can't handle file names containing spaces unless you use the quotes.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hardest part was getting all the silly spaces in the folder names right. At least I didn't have to include the path to the .net framework. Have you SEEN those silly folder names?

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You do know that all versions of Windows from XP onwards have supported [Tab] completion at the Command Prompt? So if you need to type:

CD C:\Users\Tom\Documents\Atmel Studio\Mars2Led\Mars2Led\Debug

actually type

CD C:\Us[Tab]\T[Tab]\D[Tab]\At[Tab]\Ma[Tab]\Ma[Tab]\D[Tab]

You can probably type less than 2 characters for most of those and if the thing you are looking for doesn't appear immediately just type [Tab] again to cycle through the other names in the directory that match what you have typed so far. So you might be able to type:

CD C:\U[Tab]\T[Tab]\D[Tab]\A[Tab]\[Tab]\[Tab]\D[Tab]

Similarly to type the command to invoke Make use something like:

C:\Users\Tom\Documents\Atmel Studio\Mars2Led\Mars2Led\Debug>\P[Tab]\at[Tab]\[Tab]\ma[Tab]\m[Tab]

As soon as you get to "\Program Files" you'll see MS-DOS automatically adds "" around it to encompass the space before Files.

Unix has had [Tab] completion since pussy was a kitten so this is just another case of Microsoft finally catching up with a superior operating system. ;-)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

In Windows, drag-and-drop of a folder into a command window pastes the full path within quotation marks. Type cd , drop folder, hit return.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I just realized that I was to make more or less the same post as Clawson above..

So instead of re-iterating the TAB key functionality in a CMD window, I'll vent my thoughts:

I'm not anal re command prompt. I love a good GUI IDE just as much as I love the command prompt. It's not one or the other - its both! They are complementing each other. Some stuff is best/safest/fasters/whatever done on a command line, others in a GUI. If you've ever dragged something and accidentaly dropped in some unknon place you know what I'm taling about..

Now, I am puzzled that people that are advanced enough to program such close-to-hardware and intricate devices as microcontrollers do not know the basics about using a command line. Not in derogatory sense, but thinking of the levereage lost. You are really missing out on some powerful stuff!

For those of you using command lines, here are two tips:

- When on a command line and you want a Windows explorer for the current directory/folder: just type

start .

- Going the other way depends on Windows version: Windows versions up to XP: Get Windows Powertoys, and install the "Command prompt here" toy. For Vista and beyond: Hold down shift while right-clicking a folder and you will get an alternative context menu where you can start a command prompt with that folder/directory as default.

Small stuff, but makes woring with Windoze sooo much better!

I didn't know the trick that dak644 posted. Now I do! Thank you!

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

 start .


Interesting. I've always used:

explorer .

AFAICT they have exactly the same effect.

If we're comparing DOS tips I get an awful lot more mileage from

xcopy * dest /cher

than I ever get from trying to drag/drop folders to be copied.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Cliff!

start 

starts whatever application that is associated with the files type. E.g.

start sometext.doc

usually starts MS Word and opens that document.

As I understand it, directories are associated with Windows Explorer.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It's all very well discussing the merits of the command line, but it doesn't get us anywhere nearer to the solution of the original problem, access denied and or waiting for unfinished jobs.
I see this problem in the GUI and command line on a Win7 notebook, but not on my PC, also with WIn7. Both use the same input files on Dropbox.
Jerry

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I see this problem in the GUI and command line on [...] input files on Dropbox.

There is too much going on here, too many symptoms, ways to test/workaround etc.

IMO, one thing to be done now is to collect the different symptoms, environments etc from the different reporters of the problem in this thread. I quickly browsed it but realized that for me this needs to be an evening activity - anyone up for it right now?

I'd like to see a tabular overview. For each problem reporter:
Windows version.
Version (incl SP) of Studio.
Is it a "hang" or is it "access denied"?
"Deterministacally repeatable" or intermittent?
Studio un as Administrator? (N.B.: It is nort enough to be logged in as an Adm, you must "Run as..")
Works on comand line?
Files on local drive, network drive, cloud drive (I assume Dropbox is in the cloud..)?
..and maybe more..

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think we're barking up the wrong tree and the coon is long gone. By the time the make process runs, the file or folder is already set to R/O. If somehow we can manage to catch this getting set, we might be onto something.

BDOS ERROR ON B: R/O

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JohanEkdahl wrote:
Quote:
I see this problem in the GUI and command line on [...] input files on Dropbox.

There is too much going on here, too many symptoms, ways to test/workaround etc.

I'd like to see a tabular overview. For each problem reporter:
Windows version.
Version (incl SP) of Studio.
Is it a "hang" or is it "access denied"?
"Deterministacally repeatable" or intermittent?
Studio un as Administrator? (N.B.: It is nort enough to be logged in as an Adm, you must "Run as..")
Works on comand line?
Files on local drive, network drive, cloud drive (I assume Dropbox is in the cloud..)?
..and maybe more..

Here's a bit of information. The first part is for the working system, the second for the failing system.
Windows version: Win 7 Ultimate English on a PC, Win 7 Home Premium German on a notebook. Both with latest SP and patches.
Studio version: 6.0.1996 (SP2) on both
On "Build solution" (F7) with the failing system it usually says "access denied", then "Waiting for unfinished job", but less often just "Access denied". When waiting for an unfinished job the make.exe uses 50% CPU (with Task Manager, 2 CPU notebook). Continue the build with Cancel then F7 after "Waiting...", or just F7 after "Access denied". It eventually completes the build.
The behaviour is the same whether AS is run as administrator or not (I have admin rights).
Same behaviour when run on the command line or in the IDE.
Again the same when run on a directory copy residing on the local drive, rather than on Dropbox (cloud drive).
After Clean/Build solution or Rebuild solution the error disappeared!!! Tried this several times without the error appearing again. Common behaviour, if you try to investigate a bug it disappears.
Will try some more, and report if the bug reappears.
Jerry

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
After Clean/Build solution or Rebuild solution the error disappeared
That's pretty much what I have done the last few times it happened. (Win7 64 bit home premium)

The first time I tried several things until I stumbled on the clean and rebuild fix.

Well at least I didn't lose my dignity and self respect by going down to the command line level. :mrgreen:

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Seem I found the cause of this problem.
Using process monitor, last error make.exe gets is :

16:43:49,5810198	make.exe	5780	IRP_MJ_CREATE	C:\Users\ledvinap\AppData\Local\Temp\make5780-1.bat	DELETE PENDING	Desired Access: Generic Read/Write, Disposition: Create, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: NT, ShareMode: None, AllocationSize: 0
16:43:49,5811396	make.exe	5780	IRP_MJ_CREATE	C:\prace\sw\avr\ahr\ahr\Debug\make5780-1.bat	DELETE PENDING	Desired Access: Generic Read/Write, Disposition: Create, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: NT, ShareMode: None, AllocationSize: 0

So it seems that make.exe is trying to recreate make-1.bat file before operating system finished deleting old version and file creation fails.

This is race condition, some antivirus software (or windows indexing service) is probably necessary to trigger it.

Here is some info on this problem, but no workaround: http://stackoverflow.com/questio...

Fixing make.exe should be quite easy:
1: try again after short delay when .bat file creation fails
2: use different names for each .bat file

variant 2 will create problem with some application firewalls - if you approve each file manually, you can't tick 'remember' option (this is already a problem, but there are only few confirmations during each compilation now. Using different names will trigger onfigmation for EACH file compiled)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Got it a couple days ago and just used windoze exploder to mark it all R/W.

Today, made a new project, and DIDN'T have it happen. Hmm. So much for my theory on what caused it.

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Two observations:

1. It still happens in Studio 6.1 beta.
2. It's not any FILES that are set to R/O, but the debug folder itself.

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut. 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Setting Debug folder as ReadOnly causes Makefile creation failure.
I am unable to reproduce the issue.

------ Build started: Project: AVR32MakeTemplate, Configuration: Debug AVR ------
Build started.
Project "AVR32MakeTemplate.cproj" (default targets):
Target "PreBuildEvent" skipped, due to false condition; ('$(PreBuildEvent)'!='') was evaluated as (''!='').
Target "CoreBuild" in file "C:\Program Files (x86)\Atmel\Atmel Studio 6.1\Vs\Compiler.targets" from project "C:\Users\---\documents\atmel studio\6.1\AVR32MakeTemplate\AVR32MakeTemplate\AVR32MakeTemplate.cproj" (target "Build" depends on it):
Task "RunCompilerTask"
C:\Program Files (x86)\Atmel\Atmel Studio 6.1\Vs\Compiler.targets(5,5): MakeFileGenFailureException captured - Access to the path 'C:\Users\---\documents\atmel studio\6.1\AVR32MakeTemplate\AVR32MakeTemplate\Debug\Makefile' is denied.
AVR32MakeTemplate(0,0): Error in generating MakeFile
Done executing task "RunCompilerTask" -- FAILED.
Done building target "CoreBuild" in project "AVR32MakeTemplate.cproj" -- FAILED.
Done building project "AVR32MakeTemplate.cproj" -- FAILED.

Build FAILED.
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========

:D

Pages