Hello again!
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,
- I had to change /etc/fuse.conf to allow chrooting into fuse filesystem
(it's possible that I've done something wrong previously, as I didn't
find any mentions of this step anywhere) - uncomment "user_allow_other",
- 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).
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.
BTW - can I leave the ^c^ flags in Tupfiles for Windows? Will tup just
ignore them or maybe report an error and terminate?
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.
