Hello Andras. I managed to group properly now. The actual problem was due to me not reading the example directions properly.
it states : #./submodules/sm1/Tupfile : foo.c |> gcc -c %f -o %o |> %B.o ../<submodgroup> #./submodules/sm2/Tupfile : bar.c |> gcc -c %f -o %o |> %B.o ../<submodgroup> #./project/Tupfile : baz.c | ../submodules/<submodgroup> |> gcc -c %f -o %o |> %B.o In the last line, i literally missed the syntax structure. I have fixed this now. Thanks for the help. On Wednesday, 12 February 2014 13:39:47 UTC+2, Andrew Mori wrote: > > Hello Andras. > > Thank you very much for the response. > > I have made the changes as you suggested. Just a couple points, ../../lib/ > in this case is actually still within the tup hierarchy. The custom library > I am writing is called libchassis.a and it was actually generated by tup in > the following rule : > > Tupfile > : log/*.o |> ar crs %o %f |> ../lib/libchassis.a > > I am going to try and use a group variable now and will get back to you. > thanks again! > > > > On Monday, 10 February 2014 17:32:44 UTC+2, András Kucsma wrote: >> >> Hi Andrew, >> >> If the .a files are outside the tup hierarchy, then you don't have to >> list them as inputs (tup doesn't really care about them): >> : status.o |> gcc $(CFLAGS) %f ../../lib/libzlog.a ../../lib/libchassis.a >> ../../lib/libmongoc.a ../../lib/libconfuse.a -o %o |> ../../../tests/status >> >> (You might want to group them together into a variable) >> >> Let me know if this solved your problem. >> >> Regards, >> András >> >> >> On Mon, Feb 10, 2014 at 2:14 PM, Andrew Mori <[email protected]> wrote: >> >>> Hi. >>> >>> I am new to the wonderful tool that is tup. >>> >>> I am trying to use an externally generated lib. >>> >>> My Tupfile looks like : >>> >>> include_rules >>> CFLAGS += -Isrc >>> CFLAGS += --std=gnu99 >>> CFLAGS += -L /test_proj/src/lib >>> : status.c |> gcc $(CFLAGS) -c %f -o %o |> status.o >>> : status.o ../../lib/libzlog.a ../../lib/libchassis.a >>> ../../lib/libmongoc.a ../../lib/libconfuse.a |> gcc $(CFLAGS) %f -o %o |> >>> ../../../tests/status >>> >>> Everything works fine, but there is an an error with my libchassis.a >>> file. The error reads : >>> >>> tup error: Explicitly named file 'src/lib/libchassis.a' can't be listed >>> as an input because it was generated from external directory >>> 'src/libchassis' - try placing the file in a group instead and using the >>> group as an input. >>> tup error: Error parsing Tupfile line 6 >>> >>> I have tried to get an understanding of groups via : >>> http://gittup.org/tup/manual.html >>> >>> but i cant make heads or tails of what to do next. >>> >>> Could someone provide me with an example of how to use groups? >>> >>> -- >>> -- >>> 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/groups/opt_out. >>> >> >> -- -- 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/groups/opt_out.
