User forums > Embedded development

MSP430 compiler did not listed

<< < (2/4) > >>

martonmiklos:
@MortenMacFly
Oh yes, it is a bit late at us now, so I have missed it.

Copying the GCC compiler template, and correcting the executables path does not working, because the mspgcc has several compiler specific option just like the -mmcu option for e.g.

I have checked out the latest code, and found the related code in the compilerGNUMSP430.cpp. As I seen it is not windows only, and it is looking for the executables in the /usr/local/msp430. I have linked the neccessary content to there.
I have analyzed the code further and realized that this compiler is not enabled on Linux.
So I will hack it tomorrow.

MortenMacFly:

--- Quote from: martonmiklos on April 01, 2011, 10:35:38 pm ---So I will hack it tomorrow.

--- End quote ---
I had a look into, it's actually quite simple:
Just move the inclusion of:

--- Code: ---    #include "compilerGNUMSP430.h"

--- End code ---
out of the "#ifdef __WXMSW__" section and this should probably be it.

If it works, please report back and we can do it on trunk.

(I am using Linux only if needed you know...)

martonmiklos:
I have done with it, and compiling a sample project is working.

I have some plans:
- The supported MCU's list needs some extending. It will be easy, because I have found all the possible -mmcu options int the mspgcc's source so after some regexp playing I will add them easily.
- I will improve the default compiler path looking algorithm, because most the mspgcc4's offical installer installs itself to the /opt by default.
- I will try to hack a project wizard, whith what I could add "inhouse" programming feature using mspdebug as post build or run step.

If I will be ready I will submit my work as a patch.

MortenMacFly:

--- Quote from: martonmiklos on April 01, 2011, 11:20:50 pm ---If I will be ready I will submit my work as a patch.

--- End quote ---
Great. Thank you.

martonmiklos:
I know this is not the most suitable topic to ask it, but maybe you have some idea how should I implement it:
I would like to have an associative array in the wizard script, because the mspdebug needs the MCU name in different format than the msp-gcc.
I figured out that the script is written in squirrel, but the documentation of it is very poor. According to it in the 3.0 version docs it says I can create tables in JSON format, but when using this syntax it gives me an error message at the first point. The 2.0 doc's table section is completly unundestoodable by me. The C::B docs does not says anything about the squuirrel version, but I guess it uses the 2.0 syntax

Navigation

[0] Message Index

[#] Next page

[*] Previous page