Hello, I have changed the building scripts a bit: - they are now split in several pretty standalone steps: a) fetching sources b) fetching existing binaries from svn c) building d) committing to SVN (not implemented yet) - there is more error checking - if some engine doesn't build, the process may still continue - it's possible to force rebuilding even if versions match - it should be possible to choose which engines to build, but option parsing is not implemented yet - there are many differences that influence Mac OS X building, but you should not bother about them anyway - buiding xetex disabled until we get support for 64-bit - it should be possible to build from any mac (at least in theory) - support for 64-bit architecture and fat binaries now from all the three relevant architectures I did that because there were constant problems when some of the steps failed to work and also because I had to modify the OS X part (why does Mac always need to be an exception? :). You may try to do svn up ./do_all.sh and report back about any problems that you might encounter. I would be grateful for any bug reports. This command will not commit to SVN yet, but there's VERSIONS.new that should be moved to VERSIONS and there is VERSIONS.svn that should be used as commit message, so the last step is almost-trivial to do manually as well, I just need to code it :) Mojca
On Sat, Nov 28 2009, Mojca Miklavec wrote:
You may try to do svn up ./do_all.sh and report back about any problems that you might encounter. I would be grateful for any bug reports.
This command will not commit to SVN yet, but there's VERSIONS.new that should be moved to VERSIONS and there is VERSIONS.svn that should be used as commit message, so the last step is almost-trivial to do manually as well, I just need to code it :)
Hello Mojca, It seems, that you've just coded it. Commit 637 has been done using your new "bin_commit.sh" (I've removed the comment sign on line 30 in "do_all.sh"). No problems... Thanks, Peter -- Contact information: http://pmrb.free.fr/contact/
On Sat, Nov 28, 2009 at 6:35 PM, Mojca Miklavec
Hello,
I have changed the building scripts a bit: I finally tested new scripts
- they are now split in several pretty standalone steps: a) fetching sources ok, done
b) fetching existing binaries from svn ok, done
c) building on FreeBSD I need some hacks to build pdftex and xetex, but it's unrelated
d) committing to SVN (not implemented yet) - there is more error checking untested
- if some engine doesn't build, the process may still continue untested, but nice to hear
- it's possible to force rebuilding even if versions match Not through do_all.sh.
Deeper tests coming soon. Regards -- Diego Depaoli
On Tue, Dec 15, 2009 at 01:51, Diego Depaoli wrote:
On Sat, Nov 28, 2009 at 6:35 PM, Mojca Miklavec wrote:
Hello,
c) building on FreeBSD I need some hacks to build pdftex and xetex, but it's unrelated
How ugly hacks? I have added plenty of "hacks" to build stuff on Mac OS X. If you need source patching I'm not sure if I can help (though one can always ask the developers), but if you need some extra switches let me know.
- it's possible to force rebuilding even if versions match Not through do_all.sh.
My idea was that if something goes wrong, one can still run one step after another. It should be easy to force building all the binaries through do_all.sh if you need it (but then it needs to be "--force-build" to distinguish between forcing building and forcing commiting or whatever else). Mojca
On Tue, Dec 15, 2009 at 8:00 AM, Mojca Miklavec
c) building on FreeBSD I need some hacks to build pdftex and xetex, but it's unrelated
How ugly hacks? I have added plenty of "hacks" to build stuff on Mac OS X. If you need source patching I'm not sure if I can help (though one can always ask the developers), but if you need some extra switches let me know. No, no extra switches needed. Hacks are needed by build-xetex if icu is already installed and build-pdftex to workaround some bashism.
- it's possible to force rebuilding even if versions match Not through do_all.sh.
My idea was that if something goes wrong, one can still run one step after another. It should be easy to force building all the binaries through do_all.sh if you need it (but then it needs to be "--force-build" to distinguish between forcing building and forcing commiting or whatever else). I agree. That's a great improvement, but my most welcome news is commit binary succesfully built even if some other fails.
Cheers -- Diego Depaoli
On Tue, Dec 15, 2009 at 14:05, Diego Depaoli wrote:
On Tue, Dec 15, 2009 at 8:00 AM, Mojca Miklavec wrote:
c) building on FreeBSD I need some hacks to build pdftex and xetex, but it's unrelated
How ugly hacks? I have added plenty of "hacks" to build stuff on Mac OS X. If you need source patching I'm not sure if I can help (though one can always ask the developers), but if you need some extra switches let me know. No, no extra switches needed. Hacks are needed by build-xetex if icu is already installed and build-pdftex to workaround some bashism.
Do you mean export CONFIG_SHELL=/bin/bash ? We can probably add that unless it breaks on any platform, but I guess it shouldn't (is there any reason that it's not fixed in the source of pdftex?) Mojca
No, no extra switches needed. Hacks are needed by build-xetex if icu is already installed and build-pdftex to workaround some bashism.
Do you mean export CONFIG_SHELL=/bin/bash ? We can probably add that unless it breaks on any platform, but I guess it shouldn't (is there any reason that it's not fixed in the source of pdftex?) Sorry for the delay
On Tue, Dec 15, 2009 at 3:31 PM, Mojca Miklavec
#!/bin/sh 80,81d79 < --without-mf-x-toolkit \ < --without-x \ 89c87 < export CONFIG_SHELL=/bin/bash
export CONFIG_SHELL=/bin/sh 91,96c89 < make all 2>&1 | tee make.log || true < set +x < < echo "" < echo "The last errors about otangle.web/otangle.p are harmless and can be safely ignored." < echo ""
gmake all 2>&1 | tee make.log
Cheers -- Diego Depaoli
participants (3)
-
Diego Depaoli -
Mojca Miklavec -
Peter Münster