Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

AutoDetect Yagarto?

(1/2) > >>

dasfoo:
Two Questions (meaning three or more)

1) I beleive that the Yagarto tool-chain isn't auto detected and setup by code blocks.  Is this true?

http://www.yagarto.de/

Yagarto being a pre-built tool chain for ARM that installs under Windows (only).

2a) Looking at the code I think I could probably make that happen if there is any interest.  I think for embedded people to have Yargarto and Code Blocks work together would be a big win.

2b) I notice that Yargarto puts it's path info in the the windows registry when it's installed, would it be okay for the auto detect function to look in the registry?

3) Looking over the code for detecting and setting up various compilers it looks to me like compiler detect and configuration  could be re-factored such that the compiler definitions and setup would be defined in an external config file.  Might make it easier for other compilers to be added.
 

ollydbg:

--- Quote from: dasfoo on October 25, 2010, 04:20:58 am ---3) Looking over the code for detecting and setting up various compilers it looks to me like compiler detect and configuration  could be re-factored such that the compiler definitions and setup would be defined in an external config file.  Might make it easier for other compilers to be added.

--- End quote ---
Yes, sounds reasonable, and great idea.!!!

currently, all the compiler search(Windows) is just like search the key path in the register or check the key file exist in some fixed place.

dasfoo:

--- Quote from: ollydbg on October 25, 2010, 06:48:36 am ---
--- Quote from: dasfoo on October 25, 2010, 04:20:58 am ---3) Looking over the code for detecting and setting up various compilers it looks to me like compiler detect and configuration  could be re-factored such that the compiler definitions and setup would be defined in an external config file.  Might make it easier for other compilers to be added.

--- End quote ---
Yes, sounds reasonable, and great idea.!!!

currently, all the compiler search(Windows) is just like search the key path in the register or check the key file exist in some fixed place.



--- End quote ---

Well okay then.  I'll see what I can get done in my copious spare time.  For me first order of business is to build codeblocks from source, then hack in support for Yargarto with the compiler options defined in a config file instead of hard coded. 

Questions:

Does CodeBlocks have a preferred data format for config files, AKA something like xml or yaml. 

I'm thinking each compiler should have it's own configuration file.

ollydbg:

--- Quote from: dasfoo on October 26, 2010, 12:51:59 am ---
Well okay then.  I'll see what I can get done in my copious spare time.  For me first order of business is to build codeblocks from source, then hack in support for Yargarto with the compiler options defined in a config file instead of hard coded. 

Questions:

Does CodeBlocks have a preferred data format for config files, AKA something like xml or yaml. 

I'm thinking each compiler should have it's own configuration file.


--- End quote ---

nice to hear.

Codeblocks use xml format (*.cbp, *.conf are all actually xml files), if you download the source code, you will find a Tinyxml library included in the source.

dasfoo:
Well poking at things a bit was able to install the nightly and build code blocks from sources. And compile a hello world program seems to work.

Is a start.

Well that wasn't too hard.  Seems to auto detect Yagarto Now...  Now see if works.  It looks like the GNU ARM Compiler is oldish.  The executables were arm-elf- instead of arm-none-eabi- might mean that some of the compiler settings aren't up to date

Navigation

[0] Message Index

[#] Next page

Go to full version