Compiling from source

Started by minorthreat on in TinyG Support. 10 replies, last activity Sep 14, 2012.

#3472

Hi, I was wondering if there's a guide for compiling from source.

I gave it a shot with amtel studio6 but hit a few hundred snags. What are you guys using for development? Can you share your project files on Github? thanks in advance.

Synthetos #3474

We are still using Studio4. We tried 5 and it was buggy, and ultimately more clicks to get through the dev and test cycles. We have not gone to 6 yet. If you get it running in 6 can you let us know?

Thanks

- Alden

#3479

Yeah, it's pretty special. The data type prog_char disappeared and you have to use the directive prog_mem... grrr I'll get it working.

#3484

Making some progress.  Studio 6 has a neat build from make file add on which actually worked, and adding "-Wno-deprecated-declarations -D__PROG_TYPES_COMPAT_" to the Flags covers the lost data type.  I'm still getting a few hundred

"Error 303 variable must be const in order to be put into read-only section by means of '__attribute__((progmem))'" 

I'll try throw const in front of them and see if that get me there.

Synthetos #3485

I have never seen that error because I have not tried 6. Thanks for hammering through this.

#3486

400 or so 'const' seemed to work. That is to say it compiled and it's about the right size... I don't have my board on me now so I'll test it later.

Synthetos #3487

Good news. I'll have to get the source from you. Did you use the master branch?

#3489

yup, working from the master. The port wasn't that bad really:

Add "-Wno-deprecated-declarations -D__PROG_TYPES_COMPAT_ " to the flags in the make file
Add const to anything that is PROGMEM , such as; static PGM_P const  msg_am[] PROGMEM const static char msg_am09[] PROGMEM...
Move the *getcFuncs[] table into SRAM

I'm nervous to claim success just yet tho, It builds, doesn't mean it works.

Synthetos #3491

Great. Let me know if it actually works. We should the make the changes to the code base for compatibility reasons.

#3492

Nope, not working, can connect but not responding to any commands (x1). Strange.

Back to TinyG Support or the forum archive.