Keeping compatibility across different IDEs, compilers, architectures, and OSs #33

Closed
opened 2018-08-01 15:23:13 +02:00 by yvan-burrie · 1 comment

I had a bit of trouble deciding by myself how I should set up my project upon debugging prior to inserting my changes. I use Code::Blocks with GCC compiler. You guys don't mind if I include my CBP (Code Blocks Project) file? I cannot get VS, even though I am a student. I use Windows and Linux (Raspberry), so I make sure it compiles correctly on each OS. What compiler flags should we use? C90, etc? There is only one ASM code which is x86 and, I believe, is only compatible with GCC due to syntax (AT&T vs Intel). If we ever code more ASM, perhaps it should also be ARM compatible since architecture-support is important for embedded virtual machines.

I had a bit of trouble deciding by myself how I should set up my project upon debugging prior to inserting my changes. I use Code::Blocks with GCC compiler. You guys don't mind if I include my CBP (Code Blocks Project) file? I cannot get VS, even though I am a student. I use Windows and Linux (Raspberry), so I make sure it compiles correctly on each OS. What compiler flags should we use? C90, etc? There is only one ASM code which is x86 and, I believe, is only compatible with GCC due to syntax (AT&T vs Intel). If we ever code more ASM, perhaps it should also be ARM compatible since architecture-support is important for embedded virtual machines.
yvan-burrie added the
question
label 2018-08-01 15:24:18 +02:00
Owner

You can also try VS: Community or VS: Code. Both are free and VS: Code is multiplatform. There is already some configuration committed to the repository, but there is also no problem to use other IDE you like.

You can also try VS: Community or VS: Code. Both are free and VS: Code is multiplatform. There is already some configuration committed to the repository, but there is also no problem to use other IDE you like.
yvan-burrie was assigned by belliash 2018-08-01 19:38:21 +02:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: aerscript/Aer#33
No description provided.