I had a little less success with this. I'm trying to build https://github.com/lab11/M-ulator/tree/master/simulator
When I used the explicit-variant branch, the first complaint tup had came from this Tupfile: https://github.com/lab11/M-ulator/blob/master/simulator/cpu/common/private_peripheral_bus/Tupfile#L3 It said that the ppb.c and ppb.h files were unspecified output files, which I fixed by changing the output of that rule to: : gen_registers.py | exceptions *.conf |> python %f *.conf |> $(TUP_VARIANTDIR)/ppb.c $(TUP_VARIANTDIR)/ppb.h Next it identified that the explicitly name file ppb.h was scheduled to be deleted, easy fix, change the next line to: : ppb.c | $(TUP_VARIANTDIR)/ppb.h |> !cc |> %B.o ../../../<objs> Next, it had the same complaint about this Tupfile: https://github.com/lab11/M-ulator/blob/master/simulator/cpu/Tupfile#L3 That is, that common/private_peripheral_bus/ppb.h was scheduled to be deleted. So I changed that rule to : foreach *.c | $(TUP_VARIANTDIR)/common/private_peripheral_bus/ppb.h |> !cc |> %B.o ../<objs> Unfortunately, that gave: tup error: Unable to use inputs from a generated directory (1899) that isn't written to by this Tupfile. I'm not really sure how to reconcile this? I thought it was a little bit weird that I had to specify TUP_VARIANTDIR on the outputs at all, felt like something that tup should've been able to figure out. Tested off latest from explicit-variant branch. Happy to try other things, let me know how else I can help. -Pat On Tue, Dec 1, 2015 at 2:04 PM Mike Shal <[email protected]> wrote: > On Thu, Nov 26, 2015 at 9:20 AM, Thomas Gahr <[email protected]> wrote: > >> Dammit, I think this was just my fault, my PATH was not set correctly. As >> soon as I add the folder with *.exe and *.dll of tup to PATH, it works like >> a charm - at least for my small test ;) >> > > Thanks for the feedback! It seems not having tup32detect.exe in PATH is > what was causing https://github.com/gittup/tup/issues/219, which I was > having trouble reproducing. That should be fixed now though. > > -Mike > > -- > -- > 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. > -- -- 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.
