On Wednesday 18 October 2023 at 17:47:50 +0200, Julien Stephan wrote: > Le mer. 18 oct. 2023 à 16:29, Mike Crowe via lists.openembedded.org > <mac=mcrowe....@lists.openembedded.org> a écrit : > > > > I'm trying to work out how we can make use of devtool to make our lives > > easier during development. In general it seems to work very well, but the > > way that it modifies bblayers.conf to add an absolute path to the workspace > > directory to BBLAYERS is incompatible with that file being held in a Git > > repository and shared by multiple users in multiple trees. There's a high > > risk that the file will accidentally be committed containing a path that's > > only meaningful for a single user in a single source tree. All of our other > > paths in bblayers.conf are relative to a variable that contains the path to > > the top of the source tree. > > Hi Mike, > > I think it is a bad idea to version files under the build directory.
Hi Julien, We don't version all files under the build directory, just ones that control the configuration that we want to share. We've been using OE that way for about twelve years now and this is the first time we've run into a problem. That might at least partly be because we haven't taken advantage of newer features like devtool though! We mostly avoided devtool by putting the sources that we modify heavily in submodules and used externalsrc.bbclass (with some local progressively-less-hacky modifications that I should try to upstream sometime.) > Maybe you have a specific use case that you can address in a different way? > You need to share bblayers.conf, I can see 2 options here: > - either you want your co-workers to fetch it only once, when setting > up their source tree > - or you need to frequently modify bblayer.conf because you are adding > or removing layers and want your coworkers to be up-to date > > In the first case, TEMPLATECONF is the way to go! More information > here; > https://docs.yoctoproject.org/ref-manual/variables.html#term-TEMPLATECONF We do need to modify bblayers.conf from time to time to add and remove layers. Using templates might be possible, but it would appear that this would force developers to manually incorporate changes (or just wipe their bblayers.conf file) when the template changes. Just keeping bblayers.conf under version control doesn't suffer from that problem. > In the second scenario, if this is something you *really* need, maybe > you can switch to some other tools such as 'kas' > (https://kas.readthedocs.io/en/latest/) that should be useful here. I have looked at kas in the past (and listened to podcasts about it), but it seemed to solve a different set of problems. I will look at it again. Thanks for the suggestions. Mike
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#189452): https://lists.openembedded.org/g/openembedded-core/message/189452 Mute This Topic: https://lists.openembedded.org/mt/102039990/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
