1. porting euphoria to embeded?
- Posted by coconut Sep 23, 2013
- 1411 views
I would like to port euphoria backend to an embedded platform, say PIC32MX microcontroller, which one is MIPS M4K based (32 bits). How would I proceed? I cloned the repo locally but then? This is bare metal, there is no OS, not even a kernel executive, so there is a lot of extraneous stuff not needed. No machine call, no pcre, no float and double, only integer math. What would be consisered a good pratice? I am tempted to clean out all those conditionnals that clutters the source code.
Do I create a branch? or a new repo with a different name? Considering the final result will be very different from the original.
Jacques
2. Re: porting euphoria to embeded?
- Posted by mattlewis (admin) Sep 24, 2013
- 1375 views
I would like to port euphoria backend to an embedded platform, say PIC32MX microcontroller, which one is MIPS M4K based (32 bits). How would I proceed? I cloned the repo locally but then? This is bare metal, there is no OS, not even a kernel executive, so there is a lot of extraneous stuff not needed. No machine call, no pcre, no float and double, only integer math. What would be consisered a good pratice? I am tempted to clean out all those conditionnals that clutters the source code.
Do I create a branch? or a new repo with a different name? Considering the final result will be very different from the original.
I would create a branch. This way, it should still be relatively easy to get other fixes / changes that people push into the trunk into your code.
Matt
3. Re: porting euphoria to embeded?
- Posted by coconut Sep 24, 2013
- 1327 views
How does it works? Considering that embedded euphoria for PIC32 will be a subset of euphoria and I will cleanup all #ifdef related to operating system and compilers. How modifications could be pushed to my branch? exemple if I modified be_execute.c the main branch will have a very different be_execute.c It seem to me that change made to one can't be synchronised with the other. It's more like two different things.
Frankly my knowlegde of version control system is quite limited. But it seems to me that such different sources files can't be synchronized. It looks more like 2 differents projects.
Thinking of it, I lean toward creating my own repositery on github.
Jacques
4. Re: porting euphoria to embeded?
- Posted by mattlewis (admin) Sep 24, 2013
- 1307 views
How does it works? Considering that embedded euphoria for PIC32 will be a subset of euphoria and I will cleanup all #ifdef related to operating system and compilers. How modifications could be pushed to my branch? exemple if I modified be_execute.c the main branch will have a very different be_execute.c It seem to me that change made to one can't be synchronised with the other. It's more like two different things.
Frankly my knowlegde of version control system is quite limited. But it seems to me that such different sources files can't be synchronized. It looks more like 2 differents projects.
It depends on the changes, but we merge stuff between branches all the time. I think that if you were to gut all of the Windows / Linux / BSD code, then you probably would have a difficult time merging. If you simply made it more portable so that this was just another port, it should work rather well.
Thinking of it, I lean toward creating my own repositery on github.
That would work, too, except that it would be a lot more difficult to get your changes back into the trunk, assuming that's something that we'd want to do. 
Matt
