On Fri, 2009-12-04 at 13:04 -0800, Peter Naulls wrote:
> Jan-Jaap van der Geer wrote:
> > The idea is that the third parameter takes the name of the package where
> > the appdir should be created. In that way, the appdir can be created in
> > the correct place in $D, since that what was missing was the packagename
> > from AB_PACKAGES in which the appdir should have been created.
> Ok, I'm still not entirely satisfied with this situation, but I have
> done something along these lines. The changes you suggested to your
> setvars should work.
> What I've done is to make it always create that package directory, even
> for a single package (and you no longer need AB_PACKAGES variable).
I found some that the package libpcre3 did not have the RiscPkg files in
its package, while libpcre3-dev did have them.
I think the problem is caused by the change of add-riscpkg in changeset
4289:
-D=$AB_DIR/package
+D=$AB_DIR/package/${AB_SUBPACKAGE}
Later on in add-riscpkg this code exists:
-package)
package="$param"
# Multiple packages can be put in subdirectories
# so check for a package specific directory
if [ -d "$D/$package" ] ; then
D="$D/$package"
scan_boot_file
fi
;;
This should add the correct package to $D. However, because of the
addition of ${AB_SUBPACKAGE} to $D, the path checked with the if
statement will fail and $D remains unmodified. It will therefore be the
same for all add-riscpkg commands.
I am not sure what the background is for the above change, but I suspect
it might be add-riscpkg commands that do not contain the -package
parameter. These would probably need a modification somewhere for it to
work correctly.
I am not sure but I think the best way to handle these are to revert the
above change and to add a -package to the add-riscpkg commands that do
not have this parameter.
Cheers,
Jan-Jaap
____________________________________________________________
FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your
desktop!
Check it out at http://www.inbox.com/marineaquarium
_______________________________________________
GCCSDK mailing list [email protected]
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
