https://bugs.freedesktop.org/show_bug.cgi?id=44618
--- Comment #9 from Thierry Reding <thierry.red...@avionic-design.de>
2012-01-26 23:32:19 PST ---
(In reply to comment #8)
> I think I can partially fix this with automake.
>
> Automake doesn't have a concept for host vs target $(CC)s, so you can't really
> compile a single binary on the build system which is used to produce code
> that'll be cross-compiled. So, that doesn't help, but:
While automake doesn't have built-in functionality for this, the method that
I use in the patch that I posted is rather common in projects that generate
code to be compiled at build time. Look for example at libXt:
http://cgit.freedesktop.org/xorg/lib/libXt/tree/configure.ac#n59
Or libgpg-error:
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgpg-error.git;a=blob;f=src/Makefile.am;hb=HEAD
There is also this:
http://sources.redhat.com/autobook/autobook/autobook_270.html
> I think I can add builtin_function.cpp to the BUILT_SOURCES or EXTRA_DIST
> variables so that when you do `make dist` to generate the Mesa release
> tarball,
> it'll build enough of src/glsl/* to generate builtin_function.cpp, which it'll
> then include in the tarball. The cross-compiling system will then not have to
> worry about generating it.
The problem with that is that it will break cross-compilation from a git
checkout. Also I believe the original reason for the decision to generate
builtin_function.cpp at build time was that it didn't have to be included
in the repository/tarball.
Thierry
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
