That looks pretty good. Did you see my last question about the library
dependencies? The Makefiles seem to be expecting them to be in /usr/share/...
I think we need to include the dependencies ahead of time so we can make sure
they are covered license wise.
On Feb 9, 2010, at 7:42 AM, Karl
Grant Ingersoll wrote:
BTW, I think you can start working on the build script even before the code
gets committed. That way we can do the initial commit and than almost
immediately you can add the build stuff.
I wanted to do rearrangement of source packages and structure in svn prior to
Grant Ingersoll wrote:
That looks pretty good. Did you see my last question about the library
dependencies? The Makefiles seem to be expecting them to be in /usr/share/...
I think we need to include the dependencies ahead of time so we can make sure
they are covered license wise.
I
I'm looking at what is required for ant builds of LCF, and for this I sort of want to understand accepted practices for Apache
builds of this kind.
(1) Structure
LCF will build many distinct jars, which need to be kept distinct because not all deployments can build or include all
On Feb 9, 2010, at 9:21 AM, Karl Wright wrote:
I'm looking at what is required for ant builds of LCF, and for this I sort of
want to understand accepted practices for Apache builds of this kind.
(1) Structure
LCF will build many distinct jars, which need to be kept distinct because
