PostFrontal Forum
PostFrontal Forum
LK8000_Support_Forum | Profile | Register | Active Topics | Members | Search | FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 LK8000 International Support
 Developers
 Recommended Development Environment
 New Topic  Reply to Topic
Previous Page
Author  Topic Next Topic
Page: of 2

brunotl
Pterodattilo

France
1153 Posts

Posted - 04/02/2025 :  15:05:53  Show Profile  Reply with Quote
for android target, you can use Android studio natively on OSX...

for other platform, the simpler is to use Linux VM (debian stable is good choice)

all info to setup toolchain for all platform is available on Github (more or less uptodate, be it's good start point) : https://github.com/LK8000/LK8000/wiki#compilation-environment-setup

PS : if you need help, ask, i will do my best to help you.


Go to Top of Page

NorthernLad59
Pulcino

United Kingdom
41 Posts

Posted - 04/02/2025 :  18:34:23  Show Profile  Reply with Quote
What user interface would you recommend if I go for Debian - I've always used Ubuntu in the past :-)
Go to Top of Page

brunotl
Pterodattilo

France
1153 Posts

Posted - 04/02/2025 :  22:15:57  Show Profile  Reply with Quote
I use Debian Bookworm / Gnome
Go to Top of Page

NorthernLad59
Pulcino

United Kingdom
41 Posts

Posted - 07/02/2025 :  19:01:19  Show Profile  Reply with Quote
Good progress:

I've setup a Debian 12 VM running under VMWare Workstation Pro 17 hosted by Windows 10.
I followed the instructions in the Wiki to install the necessary toolchain etc.
I tried "Netbeans" but struggled to even connect it to the native C++ compiler.
I then installed "Visual Studio Code" and have successfullt built, run and even debugged a LINUX build.
I'm hoping to target an Oudie 2 so moved onto installing the arm-mingw32ce cross compiler. I believe I have managed this and have used your recommendation to append the appropriate directory to the system PATH. Sadly the build fails but the compiler is on the PATH:

I can run the compiler from terminal in the project main directory:

richard@DebianLK8000:~/Documents/Software_Development/LK8000_STUFF/LK8000$ arm-mingw32ce-gcc
arm-mingw32ce-gcc: fatal error: no input files
compilation terminated.
richard@DebianLK8000:~/Documents/Software_Development/LK8000_STUFF/LK8000$

However when I try to build I get this output:

richard@DebianLK8000:~/Documents/Software_Development/LK8000_STUFF/LK8000$ make TARGET=PNA all
/bin/sh: 1: arm-mingw32ce-gcc: not found
expr: syntax error: unexpected argument ‘80200’
/bin/sh: 1: arm-mingw32ce-gcc: not found
expr: syntax error: unexpected argument ‘90100’
make: arm-mingw32ce-g++: No such file or directory
GCC VERSION :
CPP Bin/PNA/Window/WndMain.o
make: arm-mingw32ce-g++: No such file or directory
make: *** [Makefile:1746: Bin/PNA/Window/WndMain.o] Error 127
richard@DebianLK8000:~/Documents/Software_Development/LK8000_STUFF/LK8000$

I've installed GitKraken Desktop for easier source control, it's a tool I'm familiar with from previous commercial work. I have made no changes to any of the source files, including the makefile. I suspect it's Linux finger trouble or my lack of experience with makefile compilations, I used Visual Studio or it's predecessors for the majority of my working life.

If anyone has any ideas I'd be grateful

Cheers Richard
Go to Top of Page

brunotl
Pterodattilo

France
1153 Posts

Posted - 08/02/2025 :  00:05:20  Show Profile  Reply with Quote
can you share the output of $ arm-mingw32ce-gcc -v
Go to Top of Page

NorthernLad59
Pulcino

United Kingdom
41 Posts

Posted - 08/02/2025 :  01:30:04  Show Profile  Reply with Quote
While checking the version of arm-mingw32ce-gcc I worked out what I was doing wrong. I had 2 instances of Terminal running, one as part of Visual Studio Code, the other a separate window. I'd extended the PATH variable in the separate Terminal window and it only applied within the context of that window. When I repeated the version command in the Visual Studio Code window the compiler wasn't found. Once I executed the command "PATH=$PATH:/opt/arm-mingw32ce/bin" within the Visual Studio Code terminal window it all worked as expected. As I said in my last post "I suspect it's Linux finger trouble ...", clearly I don't understand the scoping of such variables within Linux :-) As the command history is shared between the terminal windows I'm surprised that variable such as PATH aren't. I'll do some Linux background reading. Sorry to have bothered you with this.

"make TARGET=PNA all" is happily building away and I'm off to bed.


Go to Top of Page

NorthernLad59
Pulcino

United Kingdom
41 Posts

Posted - 08/02/2025 :  11:00:16  Show Profile  Reply with Quote
FYI, I had to add libfl-dev for it to build the PNA targets using the cross compiler.
Go to Top of Page

brunotl
Pterodattilo

France
1153 Posts

Posted - 08/02/2025 :  13:52:44  Show Profile  Reply with Quote
quote:
Originally posted by NorthernLad59

FYI, I had to add libfl-dev for it to build the PNA targets using the cross compiler.



you can update github wiki page wiki
Go to Top of Page
Page: of 2  Topic Next Topic  
Previous Page
 New Topic  Reply to Topic
Jump To:
PostFrontal Forum © PostFrontal - La community del Volo a Vela Go To Top Of Page
This page was generated in 0.12 seconds. Snitz Forums 2000

Since 2006, owned and maintained by PostFrontal S.A.S. di Giuliano Golfieri & c. - VAT ID: IT05264240960
THIS WEBSITE ONLY USES FUNCTIONAL COOKIES
Privacy & Cookie Policy