> Pavel Sanda wrote:
> It was deliberate.
> For my use, xz -9 is far too slow for anything except the
> final "make dist" I run just prior to a release.
>
> For a release, I run this, via one of the
> alpha, beta or stable targets in gnulib's maint.mk:
>
> $(MAKE) dist XZ_OPT=-9ev
Is it possib
Pavel Sanda wrote:
>> Pavel Sanda wrote:
>> It was deliberate.
>> For my use, xz -9 is far too slow for anything except the
>> final "make dist" I run just prior to a release.
>>
>> For a release, I run this, via one of the
>> alpha, beta or stable targets in gnulib's maint.mk:
>>
>> $(MAKE) dist
On 11 April 2010 23:37, Bob Friesenhahn wrote:
> Yes, compression is useful. However, the cost of pushing the algorithm
> close to the limit does incur costs as well. For many packages, getting 99%
> of the max in 1/2 the time is a worthy tradeoff. This is similar to the
> decision to use -O2 as
On 02/04/10 14:37, Peter Johansson wrote:
On 4/2/10 7:04 AM, Jef Driesen wrote:
The problem I'm trying to solve is that I already have a version.h
that is generated from a version.h.in template that contains:
#define MYLIB_VERSION_MAJOR @MYLIB_VERSION_MAJOR@
#define MYLIB_VERSION_MINOR @MYLIB_
Jef Driesen wrote:
mylib_la_SOURCES += version.c
mylib_HEADERS += version.h
BUILT_SOURCES = version.h
EXTRA_DIST += $(srcdir)/version
CLEANFILES += version-t
Took me a while to figure out the escaping of the @ symbol. It seems
to work fine, except that I would like to add "$(srcdir)/version.h.
On 12/04/10 14:39, Jef Driesen wrote:
On 02/04/10 14:37, Peter Johansson wrote:
On 4/2/10 7:04 AM, Jef Driesen wrote:
I also have a corresponding version.c file that has the same info, but
for use at runtime:
#include "version.h
const int mylib_version_major = MYLIB_VERSION_MAJOR;
const int my
On 12/04/10 14:59, Peter Johansson wrote:
Jef Driesen wrote:
mylib_la_SOURCES += version.c
mylib_HEADERS += version.h
BUILT_SOURCES = version.h
EXTRA_DIST += $(srcdir)/version
CLEANFILES += version-t
Took me a while to figure out the escaping of the @ symbol. It seems
to work fine, except that
Hi,
I have an include file (named 'my_include.am') that I want to append in
all the Makefile.in of my project
as if it was included in all my Makefile.am.
I don't want to edit all the makefile.am files (even through a script)
Is there any simple way to do that ?
Thx,
--
Xavier MARCELET
Jef Driesen wrote:
On 12/04/10 14:59, Peter Johansson wrote:
Also, I would try avoid distributing
`version.h', but not sure how to do that from top of my head.
Why would you not distribute it?
Well, it's a matter of taste, but I see no real reason to include it in
the tarball.
I think it's
On 12/04/10 15:58, Peter Johansson wrote:
Jef Driesen wrote:
On 12/04/10 14:59, Peter Johansson wrote:
Also, I would try avoid distributing
`version.h', but not sure how to do that from top of my head.
Why would you not distribute it?
Well, it's a matter of taste, but I see no real reason t
On Mon, 12 Apr 2010, Pavel Sanda wrote:
Pavel Sanda wrote:
It was deliberate.
For my use, xz -9 is far too slow for anything except the
final "make dist" I run just prior to a release.
For a release, I run this, via one of the
alpha, beta or stable targets in gnulib's maint.mk:
$(MAKE) dist
Hello Xavier,
* Xavier MARCELET wrote on Mon, Apr 12, 2010 at 03:58:33PM CEST:
> I have an include file (named 'my_include.am') that I want to append
> in all the Makefile.in of my project
> as if it was included in all my Makefile.am.
> I don't want to edit all the makefile.am files (even through
Hello,
* Jim Meyering wrote on Mon, Apr 12, 2010 at 11:44:01AM CEST:
> Pavel Sanda wrote:
> >> For my use, xz -9 is far too slow for anything except the
> >> final "make dist" I run just prior to a release.
> >>
> >> For a release, I run this, via one of the
> >> alpha, beta or stable targets in g
Am Sonntag 11 April 2010 21:37:13 schrieb Andreas Jellinghaus:
> isn't xz extremely slw with -9?
> maybe it wasn't a bug, bit intentionally not used,
> as that huge extra amount of time doesn't result in
> that many bytes saved.
>
> is the compression level configureable somehow?
I did two te
Am Montag 12 April 2010 20:31:22 schrieb Ralf Wildenhues:
> My idea would be to implement this for master, and revert the recent
> xz -9 patch on branch-1.11. Comments, criticism?
if the environment variables can be used to set the compression,
that is perfect for me. why write your own code, whe
* Andreas Jellinghaus wrote on Mon, Apr 12, 2010 at 09:41:44PM CEST:
> Am Montag 12 April 2010 20:31:22 schrieb Ralf Wildenhues:
> > My idea would be to implement this for master, and revert the recent
> > xz -9 patch on branch-1.11. Comments, criticism?
>
> if the environment variables can be us
Hi All,
Is there any way at all to tweak the $VERSION that used in creating the
distdir (tarballs)? While I don't want to change the actual version of
a given package, I do want to add an identifier to the tarball. Such an
identifier would be introduced by a configure switch and thus subst'd
int
On 04/12/2010 04:50 PM, Brian J. Murrell wrote:
> Hi All,
>
> Is there any way at all to tweak the $VERSION that used in creating the
> distdir (tarballs)? While I don't want to change the actual version of
> a given package, I do want to add an identifier to the tarball. Such an
> identifier wo
It works when you switch the order of the directories in SUBDIRS.
Thanks!
I have another question regarding to the flag of the g++ compiler. I want to
debug the code carefully so I want to add -O0 option to the g++ so that it
will not optimize the code. Here is what I am doing now. I use
./confi
19 matches
Mail list logo
