Hello,
Would you consider making a GitHub account and host the code there? It is just that it would be so much easier to send and discuss patches that way instead of with a mailing list. I used buildroot before on linux and never took the time to send patches because of the procedure. Now I am on macOS so I switched to openADK which works nicely! (especially the update-patches is nice). Would you maybe be open to that?
FYI, Here is a list of issues I encountered: - raspberry pi 1 model B+ is my board. The kernel did not compile. Then I added some needed config values like from the official defconfig, and then it compiled. But it did not boot my system. Then I selected to use the supplied defconfig from the kernel, and now it boots and works. - I had some issues compiling glib-host on a latest generation macbook with Xcode 8.3.2, it seems I had an extra uuid.h file in the include directory, which made compiling fail because it was not using the one from my system. Then it did not link to the AppKit framework in the end, which I fixed with setting the HOST_LDFLAGS in the package - qtbase: seems I needed to apply the patch in attachment to make it compile with Qt 5.7.0, which is taken from 5.9. Also, the detection of the xcodebuild needed to be fixed.
Best regards Tom,
Hi Tom, Tom Deblauwe wrote,
Hello,
Would you consider making a GitHub account and host the code there? It is just that it would be so much easier to send and discuss patches that way instead of with a mailing list. I used buildroot before on linux and never took the time to send patches because of the procedure. Now I am on macOS so I switched to openADK which works nicely! (especially the update-patches is nice). Would you maybe be open to that?
No, sorry. I like selfhosting of my open source projects. I have seen Sourceforge from the beginning and then Google-Code... But you can simply use GOGS? https://gogs.waldemar-brodkorb.de/linux/openadk
Or you use the github mirror, I will manage to get your patchsets/pull requests included. https://github.com/wbx-github/openadk
I need to fix my automatic sync mechanism. But I pushed now all changes.
FYI, Here is a list of issues I encountered: - raspberry pi 1 model B+ is my board. The kernel did not compile. Then I added some needed config values like from the official defconfig, and then it compiled. But it did not boot my system. Then I selected to use the supplied defconfig from the kernel, and now it boots and works.
Raspberry PI kernels are always a bitch. The rpi2/rpi3 OpenADK mini.configs are working fine again. I need to sync and test rpi1 again. Thanks for the report.
- I had some issues compiling glib-host on a latest
generation macbook with Xcode 8.3.2, it seems I had an extra uuid.h file in the include directory, which made compiling fail because it was not using the one from my system. Then it did not link to the AppKit framework in the end, which I fixed with setting the HOST_LDFLAGS in the package
May be you can sent a pull request for that.
- qtbase: seems I needed
to apply the patch in attachment to make it compile with Qt 5.7.0, which is taken from 5.9. Also, the detection of the xcodebuild needed to be fixed.
Should we update to QT 5.9?
best regards Waldemar
Hello,
On 8 May 2017, at 17:57, Waldemar Brodkorb wbx@openadk.org wrote:
No, sorry. I like selfhosting of my open source projects. I have seen Sourceforge from the beginning and then Google-Code... But you can simply use GOGS? https://gogs.waldemar-brodkorb.de/linux/openadk
Ok thanks looks very good too!
- I had some issues compiling glib-host on a latest
generation macbook with Xcode 8.3.2, it seems I had an extra uuid.h file in the include directory, which made compiling fail because it was not using the one from my system. Then it did not link to the AppKit framework in the end, which I fixed with setting the HOST_LDFLAGS in the package
May be you can sent a pull request for that.
I will check, however, I don’t know where the extra uuid.h file came from, and I just deleted it manually.
Should we update to QT 5.9?
It compiles fine with the patch, and 5.9 is not yet released, so I would wait a bit. Maybe updating from 5.7.0 to 5.7.1 would be a better effort.
I have one question still that puzzles me that I could not find in the docs. I did find that you are supposed to save your .config file as a means to share full configs. But what if like now, I have started with raspberry pi 1, and then I selected some packages, e.g. boost and some utils I like to have. Then I want to change to raspberry pi 3 as a system. How would I do that best?
Would I just start from scratch, make menuconfig, select arm->pi3 and save the config. And then like do a diff between the pi3 .config file and the full pi1 .config file?
Or should I create a task somehow… And can I easily create one from a given .config, or what is the best way to create such a task?
Thanks, Best regards Tom
Hi Tom,
Am 10.05.2017 um 10:15 schrieb Tom Deblauwe deblauwetom@gmail.com:
Hello,
On 8 May 2017, at 17:57, Waldemar Brodkorb wbx@openadk.org wrote:
No, sorry. I like selfhosting of my open source projects. I have seen Sourceforge from the beginning and then Google-Code... But you can simply use GOGS? https://gogs.waldemar-brodkorb.de/linux/openadk
Ok thanks looks very good too!
- I had some issues compiling glib-host on a latest
generation macbook with Xcode 8.3.2, it seems I had an extra uuid.h file in the include directory, which made compiling fail because it was not using the one from my system. Then it did not link to the AppKit framework in the end, which I fixed with setting the HOST_LDFLAGS in the package
May be you can sent a pull request for that.
I will check, however, I don’t know where the extra uuid.h file came from, and I just deleted it manually.
Should we update to QT 5.9?
It compiles fine with the patch, and 5.9 is not yet released, so I would wait a bit. Maybe updating from 5.7.0 to 5.7.1 would be a better effort.
I have one question still that puzzles me that I could not find in the docs. I did find that you are supposed to save your .config file as a means to share full configs. But what if like now, I have started with raspberry pi 1, and then I selected some packages, e.g. boost and some utils I like to have. Then I want to change to raspberry pi 3 as a system. How would I do that best?
Would I just start from scratch, make menuconfig, select arm->pi3 and save the config. And then like do a diff between the pi3 .config file and the full pi1 .config file?
Or should I create a task somehow… And can I easily create one from a given .config, or what is the best way to create such a task?
There is no automatic way right now. You simply copy an existing task and modify to get all packages preselected and configration data set. Any file in the task directory will show up in menuconfig.
Then you generate a valid config before building with something like that: make ADK_TARGET_ARCH=arm ADK_TARGET_SYSTEM=raspberry-pi3 ... (libc, filesystem, task) defconfig
You got the idea behind?
best regards Waldemar
There is no automatic way right now. You simply copy an existing task and modify to get all packages preselected and configration data set. Any file in the task directory will show up in menuconfig.
Then you generate a valid config before building with something like that: make ADK_TARGET_ARCH=arm ADK_TARGET_SYSTEM=raspberry-pi3 ... (libc, filesystem, task) defconfig
You got the idea behind?
Ok, so that is good to know, I will use that!
I like it.
Thanks, Best regards Tom,
Hi Tom, Tom Deblauwe wrote,
Hello,
FYI, Here is a list of issues I encountered:
- raspberry pi 1 model B+ is my board. The kernel did not compile. Then I added some needed config values like from the official defconfig, and then it compiled. But it did not boot my system. Then I selected to use the supplied defconfig from the kernel, and now it boots and works.
I fixed the mini.config for rpi today. git pull. I tested the result on a raspberry pi.
best regards Waldemar
-
Tom Deblauwe -
Waldemar Brodkorb