-
Type: Task
-
Resolution: Done
-
Affects Version/s: None
-
Component/s: None
-
None
@agorrod, @michaelcahill, sueloverso – here's a set of changes that mostly makes the tree build with automake 1.14.
It's not complete, I'm just pushing this branch so we have something to talk about.
The big change I saw is configuring automake with subdir-objects. Automake 1.14 wants object files built in the source directories (it will be the default in automake 2.0, and you get a warning error if you don't do so in 1.14).
This change means that if you build in build_posix (as I do), you get a tree under build_posix that mirrors the source tree:
src/support src/support/.deps src/support/.deps/.dirstamp src/support/.deps/cksum.Plo src/support/.deps/err.Plo src/support/.deps/filename.Plo ... src/support/.deps/stat.Plo src/support/.dirstamp src/support/.libs src/support/.libs/cksum.o src/support/.libs/err.o src/support/.libs/filename.o ... src/support/cksum.lo src/support/cksum.o src/support/err.lo src/support/err.o src/support/filename.lo src/support/filename.o
If you build in the top-level directory (as some of you do?), you get those files in the source tree itself, alongside the C language source files.
I don't think we care where people downloading our distributions build their files, but this might be a problem for us, if we want to work in trees where we build in the top-level, suddenly the source directories have a lot more stuff.
I didn't get Java to build, but I think everything else is working. There's some magic in the Java build I didn't figure out, specifically, $(JAVASRC) isn't working with automake 1.14. I had to make a change in test/format to not use $(top_srcdir) to find a source file (see 6d8c107), and I suspect a similar change is going to be necessary for Java.
- is related to
-
WT-599 Fix future incompatibility with automake
- Closed