> > As a mostly-Windows user I haven't yet tried tup on Linux, until today (; > So I've faced the whole palette of problems that most of you faced before: > - I had to set suid in tup binary and modify the tupfiles with ^c^ flag to > be able to debug the project with GDB, >
Yep :( - we should be able to fix that so that it works out of the box. > - the build time incresed by over 100% - from about 25-30s to about > 60-70s, making it much closer to what I have on Windows (about 90s if I > remember correctly). > Build time increased by over 100% compared to what? > > Of course all of this is to enable debugging. I use Eclipse and I hoped > that "path mapping" would allow me to somehow walk around the problem, but > it's not possible to configure path mapping with wildcards or regexes and > entering several hundred entries for each tupjob-xxxx seemed a bit stupid. > I reported a feature request to Eclipse, but I don't have high hopes for > it... https://bugs.eclipse.org/bugs/show_bug.cgi?id=444816 > > If only tup could be limited with the IDs to some reasonable number (like > the number of CPU cores) the path-mapping approch would be feasible. > Ahh, yeah - right now I think the tupjob number is just the tupid, which is essentially the row that gets added to the database. I don't see why we couldn't just use a job slot number (1 - #cpus) and map that to the tupid instead. Though if we end up just using a namespace the problem may go away anyway. > > BTW - can I leave the ^c^ flags in Tupfiles for Windows? Will tup just > ignore them or maybe report an error and terminate? The flag just gets ignored by Windows, so feel free to leave it in for now. Hopefully it will do nothing on Linux some day as well :) -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.
