Sysprogs forums › Forums › VisualGDB › Log : cross-compiling openFrameworks to Raspberry Pi using VisualGDB
This topic contains 10 replies, has 2 voices, and was last updated by elliotwoods 1 year, 1 month ago.
April 19, 2022 at 01:02 #32525
I’m going to make a bit of a project log here for trying to compile openFrameworks creative coding toolkit for Raspberry Pi using VisualGDBApril 19, 2022 at 01:05 #32526
I couldn’t get the Makefile system working. I tried:
- Importing the project
- Using the ‘make’ command that comes with the VisualGDB toolchain against the Makefile in the oF emptyExample app
Instead, I’m trying now using MSBuild (which means setting everything up from scratch).
First step is to get openFrameworks to build. I noticed that adding paths like
/usr/include/gstreamer-1.0to the include path doesn’t have any effect (includes don’t search the system paths?), you need to use the absolute path of the copy on your own computer, e.g.
C:\dev\VisualGDB\rapsberrypi-buster\arm-linux-gnueabihf\sysroot\usr\include\gstreamer-1.0April 19, 2022 at 01:30 #32527
There seems to be some auto-path adder?
For some reason the props file didnt’ work for the emptyExample app – but then this pop up came alongApril 19, 2022 at 01:32 #32528
Ah there does seem to be some kind of layout to this:
=/usr/include/cairoApril 19, 2022 at 02:04 #32529
These relative paths seem to work from inside the .props file.
All source files are building now.
Working on the libs.
App builds, now we want to try and see it running…April 19, 2022 at 02:06 #32530
Now the emptyExample works at https://github.com/elliotwoods/ofxVisualGDBCrossCompileApril 19, 2022 at 03:53 #32532
Had a lot of trouble with precompiled headers, e.g.:
April 19, 2022 at 05:16 #32533
- The precompiled header needs to be an absolute path in the project settings
- If the path for the precompiled header is anything other than adjacent to the project file itself, then it doesn’t seem to work
Still having trouble with pre-compiled headers, even when both pch.cpp and test.cpp are in the same folder as the Project file
Failed to compile test.cpp. arm-linux-gnueabihf-g++.exe exited with code 1
========== Project Build Summary ==========
LaserClientGDB built in 00:03
========== Build: 0 Succeeded, 1 Failed, 0 Skipped ==========April 20, 2022 at 10:11 #32537
You can find a detailed tutorial explaining the use of precompiled headers here. If it doesn’t work with your project, we would advise following the tutorial to get a working project, and then comparing the 2 projects side-by-side.
If you can pinpoint a specific setting that is not working as expected, feel free to let us know and we will help you find a workaround.April 24, 2022 at 19:05 #32552
Thank you .
I was able to get PCH working with simple projects (e.g. as per the tutorial you linked), but so far not with more complicated projects.
- The error message is pretty empty (as seen in my previous message)
- There are no obvious causes
- I’ve tried a few different approaches (e.g. only having once cpp file ‘using’ the PCH. Tried different folder layouts) and still see failures
I think the next step would be to step-by-step increasingly add all my complications to a bare project until the PCH fails. I don’t have time for that right now, but I’ll be sure to update here if I find something.
elliotApril 24, 2022 at 19:06 #32553
Also for refence, here’ a link to the matching forum post over at openFrameworks:
Cross compiling for Raspberry Pi from Windows – arm – openFrameworks
You must be logged in to reply to this topic.