Hello Robert, > Is there a reason to have more than one version in ptxdist at one time? > If not, we shouldn't make it configurable, because maintenance effort > explodes then. If yes, it can be done. Note that, if a new version is > available, it can be changed in the .make file. But making it > configurable suggests that projects may work with any possible version.
OK, I will change it. >> Can I have access somehow to the git tree? That would be easier to >> develop and provide patches. > > Marc has his own git tree and shadows the svn. > http://git.pengutronix.de/?p=mkl/ptxdist;a=summary Is there a clone url ? >> Just curious, why is there an SVN tree if you are developing the tree >> with git anyway? > ptxdist is developed with svn since ages. git is shiny and new and has > it's own class of possibilities and problems. People are free to use it, > but the central repository remains svn for now. I did not ask you to move to git... I just thought it was currently the opposite around, that the svn tree was generated from git these days... My mistake. > Note that, if you want to generate a dependency, the packet label has to > do the select, not a packet option. > config FOO > bool > prompt "foo" > select BAR if FOO_BAR > > if FOO > > config FOO_BAR > bool > prompt "bar option to foo" > > endif Clear! > Looks like missing selects. Can you do the following: > - try to identify the packet in question > - ptxdist clean your project > - ptxdist targetinstall only the suspicious packet I will look into it, I might come up with some patches :-) > Don't add dependencies in the makefiles, they have to be done in the .in > files with select statements. > Note that, for example, we plan to generate ipkg dependencies from the > dep tree as well, and in order to do so, we have to have all deps in the > kconfig system. Clear! Kind Regards, Remy -- ptxdist mailing list ptxdist@pengutronix.de
