Re: [Openexr-devel] Building custom OpenEXR

[Piotr Stanczyk]

+1 on what Nick just said.

I think I may have missed that detail in your earlier message. However, I am curious as how you got configure to work at all since a new clone will not contain the file.

To sum up: if you clone from github then be sure to run bootstrap before running configure (it's also prudent to do this if you are switching branches) If you get the tarballs then you can omit the bootstrap command.

Piotr

---

From: Nick Rasmussen address@hidden
Sent: 14 August 2012 19:02
To: Larry Gritz
Cc: Piotr Stanczyk; address@hidden
Subject: Re: [Openexr-devel] Building custom OpenEXR

If you're developing from the repository, or download from one of the github tags,
you need to run bootstrap first to generate the configure script and Makefile.in files.
After that and a configure, it's usually smart enough to re-run automake if you change
a Makefile.am.  This is mentioned in the README.CVS file, which we should probably
rename to README.GIT :)

The official release tarballs are generated by using 'make distcheck' which guarantee
that the distribution is self-consistent and passes all the tests.  It also performs all the build
steps up to the configure step, so it's not required to have automake installed to build
the release tarballs.

-nick

On Tue, Aug 14, 2012 at 5:12 PM, Larry Gritz <address@hidden> wrote:

Yes, that did seem to fix it.

Is 'bootstrap' supposed to be the first step to building, after unpacking the tarball or checking out from the git repo?  Did I misunderstand by thinking that ./configure was the usual starting point?

On Aug 14, 2012, at 4:54 PM, Piotr Stanczyk wrote:

> I'll reproduce your steps in a moment. In the meantime, could I ask to see if running bootstrap before the configure 'fixes' the installation issue?
>
> Piotr

--
Larry Gritz
address@hidden



_______________________________________________
Openexr-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/openexr-devel