[yocto] [bitbake] Issue with SVN fetcher options

Karim ATIKI karim_atiki at hotmail.com
Mon Oct 10 06:47:58 PDT 2016


OK.


I found  out the solution.


Actually, I noticed in the log file "log.do_fetch()" that the SVN command finishes with the "module" name as the output directory.

I took a look to bitbake sourcecode and realized that the parameter I was looking for in the SRC_URI was "path_spec".


ThereforeI changed the SRC_URI with:


SRC_URI = "svn://${PGA_SVN_USERNAME}:${PGA_SVN_PASSWORD}@our-server:22037/svn-atonce/subproject/;module=trunk;protocol=http;path_spec=subproject"

And everything works fine.
Please note that there are no mentions of "path_spec" in the the BitBake manual nor Yocto MegaManual.

I just wonder if there's a reason for that. Anyway, it solved my problem.

Cheers.

Karim


________________________________
De : yocto-bounces at yoctoproject.org <yocto-bounces at yoctoproject.org> de la part de Karim ATIKI <karim_atiki at hotmail.com>
Envoyé : lundi 10 octobre 2016 15:11
À : yocto
Objet : [yocto] [bitbake] Issue with SVN fetcher options


Hi all,


I'm writing a recipe to build a custom project for an ARM based board (Colibri T20).

I need to fetch the different sub-projects from SVN and launch the respective makefile.


However, I'm experiencing a problem with the SVN fetcher of bitbake.

Indeed, my URI looks like:


SRC_URI = "svn://${PGA_SVN_USERNAME}:${PGA_SVN_PASSWORD}@our-server:22037/svn-atonce/subproject/;module=trunk;protocol=http"

Basically, it works fine. But the source code is fetched into:

../downloads/svn/our-server:22037/svn-atonce/subproject/trunk


And I need it to be checked out into a local directory as follow:


../downloads/svn/our-server:22037/svn-atonce/subproject/

I haven'nt found yet an option for the SVN fetcher to specify a local directory for the check-out.

Is there an option that I haven'nt found in the BitBake manual ?

Cheers.

Karim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20161010/874b49ec/attachment.html>


More information about the yocto mailing list