Juergen Beisert wrote:
> Hi Gary,
>
> On Wed, Nov 26, 2008 at 05:13:26AM -0700, Gary Thomas wrote:
>
>> I've seen that I can put almost anything in my project tree
>> that mirrors the basic tree (e.g. rules/*.in show up in the
>> menu).
>>
>> How can I specify a directory for my sources that's also
>> local to my project (I always keep the staged sources around,
>> so I'd like to just populate the project with them + these
>> source tarballs will not be public in any way)
>>
>> Is there a macro (like PTXDIST_TOPDIR) that I can use to mean
>> the current [staged/cloned] project path?
>>
>
> Did you read
> http://www.pengutronix.de/software/ptxdist/appnotes/AppNote_WorkWithSources.pdf.
> Maybe it will do the trick.
>
Thanks, this helped. That said, I still need more :-)
I package up the PTXdist system for use by my customers. Part of this
packaging
includes creating specific configurations (projects) and pre-staging all of the
source
tarfiles for all the packages in those projects. That way, I can deliver the
whole
setup and know that it will build, even without any access to network resources
(you can only imagine some of the places that want to use such tools, but don't
allow their people to access "the net" :-)
In addition, there may be customers that need additional packages. I've been
able to
add customized rules and p*config files for them (really just an extended
project
tree). The problem then comes from where to get the source files, as I don't
want
this project to have to add files to the common source repository - it's stored
off
in "/opt/xxx/lib/ptxdist-1.99.svn/src" and typically not writable by the
user/customer.
Is there any way I can extend my customized project so that the majority of the
[staged] source files come from the principle repository (in /opt) and the
customer
specific ones come from the project tree itself?
To be clear - the principal setup is like this:
/opt/xxx/lib/ptxdist-1.99.svn/
.../rules
.../scripts
... etc
.../src
A customer project might look like this:
/home/customer/ptx_project/
.../selected_ptxconfig
.../selected_platformconfig
.../projectroot
.../rules
.../src
Just as I can extend the package set via 'rules' (thanks, BTW,
this is a great improvement!) in the project, I'd like to extend
the source repository.
So far, I've not figured out how to make this work.
Ideas? Comments?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
ptxdist mailing list
[email protected]
