AS6 Clone Debug configuration to Release

Go To Last Post
5 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

How do I copy/clone one configuration to another in AS6?

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

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

What do you mean? The whole point of VS2008 having "Debug" and "Release" is so you can have two sets of project configuration. Typically "Debug" enables things like the embedding of symbolic info, stack checking and so on while "Release" produced slimmed down/"faster" code for actual deployment. So what would be the point of making one identical to the other?

In fact you are not limited to two - it's just that the default happens to be two and they happen to be called "Debug "and "Release" but you can mamage this - add/remove ones - have ones for things like "Lint build" or "Profile build" etc.

If the Debug/Release thing is a source of confusion I imagine (untested) that you can actually remove one so there is only one build variant and no potential for inadvertently selecting the wrong choice.

EDIT: Yup Build-Configuration Manager allows you to remove build variants you don't want see picture:

Attachment(s): 

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

Quote:

How do I copy/clone one configuration to another in AS6?

When creating a new configuration, when you give the name, you have the option to create a empty configuration, or copy from any of the existing ones

Attachment(s): 

:: Morten

 

(yes, I work for Microchip, yes, I do this in my spare time, now stop sending PMs)

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

OK. This is what I tried before I posted.

I deleted the Release config and recreated it with copy settings from Debug. It failed to copy the settings from the debug config - specifically the Toolchain settings. Is this a bug in AS6? I have no problem with cloning configs in VS2008 - VS2012.

The reason I wanted to do this is that I had started to create a project with release settings but in the debug config. I didn't want to have to make the changes one by one again.

The solution was to edit the .cproj xml file and copy the settings from one config to the other.

Now I can make the changes that I require in the Debug config.

I can also go to bed now. :wink:

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

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

The whole Debug/Release thing is inherited from PC work and is pretty pointless for AVR anyway. IN the PC world you are concerned whether the final output binary (.exe) is 57K or 384K. "Release" builds the small one and "Debug" builds the large one. The large one (and the small one come to that) are more like a .ELF file than a .HEX file in that they have the potential to include loads of debug info with symbolic links to source files and so on.

Meanwhile in the AVR world the final binary is created by extracting ONLY the binary opcodes from a .elf file to a .hex file so the binary produced for either "Release" or "Debug" are almost exactly the same (unless you choose to vary optimisation level?). So the whole reason/complication of having "Debug"/"Release" in the AVR world is all a bit pointless. They should really just call them "compiler/linker config 1" and "compiler/linker config 2" as all they are really doing is giving you a couple of sets of configuration for those tools but it's not really a question of "Debug" and "Release".

What's more most beginners don't even seem aware that there are two and of those that are many do not really understand the difference so, like I say, a pointless confusion trying to apply a Win386 .exe view of the world on AVR development.