I wouldn't be asking the question if it did :D.
EXAMPLE:
#sample project
mkdir 1 && cd $_
echo 'int foo() { return 42; }' > 1.c
echo ':1.c |> cc -c %f -o %o |> 1.o' > Tupfile
tup init
tup
#copy sample into ../2 (includes .tup)
cp -a . ../2
cd ../2
tup # this triggers a rebuild even though it shouldn't -- 2 is an exact
copy of 1 and 1 (and therefore 2 as well) is already built
cd ../1
cp -a ../2 .
tup #tup error: Attempting to insert '1.o' as a generated node when it
already exists as a different type (normal file)
rm 2/1.o #fixes the issue
On Thursday, July 2, 2015 at 3:30:44 PM UTC+2, Freddie Chopin wrote:
>
> On 02.07.2015 12:57, Petr Skočík wrote:
> > How can I copy B along with the build products and convince tup that
> > the build products are correct and up to date.
>
> I think you should copy .tup/ hidden folder along with the sources and
> generated files - maybe that way it would work fine?
>
> Regards,
> FCh
>
--
--
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
options: http://groups.google.com/group/tup-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.