Hi!

I am a beginner to bitbake and openembedded, so please bear with me.

In short, I have a custom system where I want to fetch all source code from a 
Gerrit server using the (Google) repo tool.
So, after repo init and sync, all source code is populated in my workspace 
(thus, bitbake doesn't have to fetch or patch the sources).
The SW modules themselves use regular CMake, make, or autotools for building.
The workspace looks like:
(workdir)/subsystem_A/SW_module_1
(workdir)/subsystem_A/SW_module_2
(workdir)/subsystem_B/...
(workdir)/product_X/meta-...     (this is were all bitbake files are stored in 
order to build product X)
(workdir)/product_Y/meta-...     (this is were all bitbake files are stored in 
order to build product Y; common configs/recipes will be a common product layer)
In product_X folder, I also plan to have a script that sets up the build env 
(similar to oe-init-build-env), creating folder:
(workdir/build/
and populate it with bblayers.conf and local.conf. bblayers.conf will add the 
layers at (workdir)/product_X/meta-...
>From here, the building of the SW modules as well as the final image takes 
>place using bitbake.
The end result of the build is a ext4 file system image, which is flashed onto 
target device.

First basic question:
How do I properly set SRC_URI in the recipes to point to the SW_modules above, 
with no fetching/patching. Can I avoid that bitbake
copy the source files to the build/tmp folder?
I don't want to list the source files in the recipe really, I just want to 
refer to folder (workdir)/subsystem_A/SW_module_1
as the CMakeLists.txt (for CMake) tells which files to build etc. Thus, 
"file:://" doesn't sound a good idea.
I want to use inherit cmake and DEPENDS for managing deps.

Thanks!
Mike
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#151157): 
https://lists.openembedded.org/g/openembedded-core/message/151157
Mute This Topic: https://lists.openembedded.org/mt/82510510/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to