On Tue, May 05, 2015 at 04:41:04PM +, Andy Falanga (afalanga) wrote:
> I am wondering what techniques are considered most useful for managing
> multiple installation of versions. For example, my team produces a C++
> library which we provide both a C++ and a python API. A couple of our
> cons
Hello Alessandro,
On Tue, Jun 24, 2014 at 01:19:02PM +0200, Alessandro Salatiello wrote:
> lib_LTLIBRARIES = libnavigation.la
> include_HEADERS = \
> some_headers.h
>
> libnavigation_la_SOURCES = \
> some_sources.cpp
>
> libnavigation_la_LDFL
On Tue, Oct 23, 2012 at 06:35:20PM +0100, Rudra Banerjee wrote:
> looks like no way (yet)!
No way (I'd say, ever) for autotools since -- as others have already
written -- they have a very different scope.
After you ask about apt-get -- why, you already can 1.
dpkg-checkbuilddeps to see missing de
On Thu, Sep 20, 2012 at 04:38:36PM -0700, Too, Justin A. wrote:
> Ease of "installation" for end users. Specifically, we have 40 identical
> machines with the same tool chain. Our developers are using these
> systems. It's a hassle to require each developer to install our project
> for non-devel
On Thu, Sep 20, 2012 at 04:03:11PM -0700, Dan Kegel wrote:
> There's a lot of naysaying going on here, but don't assume that a single
> properly built binary can't be made to run on a large number of systems
> until you've looked into it carefully. All you have to do is target the
> lowest common
On Thu, Sep 20, 2012 at 10:24:28AM -0700, Too, Justin A. wrote:
> I would like to build and distribute a pre-built binary package for my
> project
For which OS / distribution?
> that can be dropped into any "installation" location.
What do you mean by "installation location"?
With kind regard
Hello Bob,
On Tue, Aug 07, 2012 at 10:42:24PM -0500, Bob Friesenhahn wrote:
> >I've tried to use a Windows compiler (WindRiver Diab) with automake
> >under cygwin. The compiler gets cygwin-style paths (/cygdrive/c/...) on
> >its command line and fails. How can I make automake use cygpath for
> >co
Hello,
I've tried to use a Windows compiler (WindRiver Diab) with automake
under cygwin. The compiler gets cygwin-style paths (/cygdrive/c/...) on
its command line and fails. How can I make automake use cygpath for
compilation (prog_SOURCES) and linking (prog_LDADD)? I see that there is
e.g. .S.ob
On Mon, Nov 28, 2011 at 05:52:22PM +0100, David Boesner wrote:
> In English: Datei oder Verzeichnis nicht gefunden = File or directory not
> found
You can run LC_ALL=C make so that you don't have to translate the
messages.
> My makefile (the one which is in the same directory like
> the gtspiC
itching branches. May this be
included in automake?
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
on Eclipse mailing lists. You may want
to publish your sources somewhere on the web, perhaps someone would have
a look.
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
ave formulated dependencies for not only test programs, but
> also test results)
Can't automake do the former automatically? Could you give an example
use case for the latter?
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
t I split the building
> and running of check_PROGRAMS and still use the generated
> parallel-tests using TESTS? Thanks.
There are also these ways:
http://www.opensubscriber.com/message/automake@gnu.org/2136673.html
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
ything after
checking out. Are these use cases supported in the your development
version?
Thanks,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
data-am?
2. Python files being first installed, and then compiled?
As a naïve user with C background, I'd expect "make" to compile the
files, "make install" -- to install. This way one could make nodist_
work, too. What do you think?
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
e belongs
> installed in $(pythondir) with `noinst_'. Note that noinst_PYTHON files
> will not be byte-compiled, though.
Ah. Any way to have compilation, but no distribution?
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
, how can I exclude the source .py files from the installation? I've
tried nodist_nobase_python_PYTHON, but that doesn't seem to do what I
want.
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
r /usr/lib/python2.5/site-packages/pkg.
How can I do that?
Thanks in advance,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
ate the file atomically?
> >
> > I'm aware of the limitations of this approach. Do you see an alternative
> > for the described use case?
>
> Complain to the vendor?
I am the vendor, in a sense :) -- the code originates from a previous
employee. I have no problems t
ut
> Cygwin. If somebody could test it, I'd be interested to hear results.
> Of course I'd also accept a patch to make it work with MinGW (using the
> 'cmd //c' idiom for translating paths, for example).
Good to know, thanks for the info! I'll try that if I manage to solve
other problems.
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
thods, such as running 'makedepend'.
That is exactly what I asked for! Great to know automake supports this!
Meanwhile, I've found out that the command line help of Tasking's
front-end tool, cc166, doesn't mention all back-end tool options; it
turned out the C++ compiler, cp166, does support dependency generation.
Wow.
While we are at it, does Visual Sudio's cl support dependency
generation?
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
solution.
Thanks in advance,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
Hello,
I've just installed automake 1.10 and found the difference between
AM_CFLAGS, CFLAGS, and mumble_CFLAGS. Again, many thanks to all
developers and contributors!
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
lean is a hammer for that.
>
> Hope that helps.
It does, thanks!
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
|xargs rm; ./config.status to
fix this. Is there a way to detect and fix this in the autotools?
I use autoconf 2.61, automake 1.9.6, and libtool 1.5.22.
Thanks in advance,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
m very sorry for the
> misinformation.
No problem, the info is still interesting. At least the lexer is
generated in the source directory. Other ideas why?
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
ding.
Neither one helped.
I assume the difference shouldn't be the fact that you generate C++
source. What else could affect the behavior? Which version of automake
do you have? Do you have ylwrap in $(top_srcdir)?
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
y.
Thanks for a quick answer! However, this didn't work for me. I've tried
putting them to both $(top_srcdir) and $(top_srcdir)/subdir. My .l and
.y files are in the latter, and this is where I want to have the
generated files, too. Further ideas?
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
irectory as the source. How can I do that?
I've tried specifying -o in AM_YFLAGS, but this, as expected, breaks the
build completely.
Thanks in advance,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
On Mon, Dec 12, 2005 at 09:28:54AM +0100, Roesner Thomas wrote:
> "does not work" means, that the linker can find all refered symbols in
> the dynamic scenario, but that there are some unresolved symbols in
> the static scenario.
As Ralf said, it's most probably the library order, I'd also suggest
Hello Ralf,
On Sat, Dec 10, 2005 at 09:22:12AM +0100, Ralf Corsepius wrote:
> You are miss interpreting automake's tasks. Packaging is not of
> automake's business.
>
> Your approach isn't much more but a short-cut to your personal and local
> practice and setup. It is wrong and therefore inappli
Hello Brendan,
On Fri, Dec 09, 2005 at 04:18:10PM -0500, Jacobs, Brendan D. wrote:
> We'd like to be able to do "make test" and
> "make release", and have automake just make the make release libraries
> and programs versus using test programs, respectively. Is there any
> support for user-specifi
Hello Thomas,
On Fri, Dec 09, 2005 at 04:25:42PM +0100, Roesner Thomas wrote:
> The point is, that I want to build all programs with shared libraries,
> but one with static libraries, wich are based on the same sourcecode
> than the shared libraries. Adding "myprog_LDFLAGS = -all-static" does
> no
Hello Ralf,
On Tue, Sep 20, 2005 at 10:56:29AM +0200, Ralf Wildenhues wrote:
> echo "m4_include([$file])"
Aha, I'd tried it with "include". Thanks!
> You need aclocal from Automake >= 1.8 for this, I believe.
I put the macros into the autoconf-Java directory and used m4_include.
This worke
Hello Alexandre,
On Wed, Sep 14, 2005 at 12:38:29AM +0200, Alexandre Duret-Lutz wrote:
> You mean building $(check_PROGRAMS) without executing the dejagnu tests?
>
> Just add your own rule that depends on $(check_PROGRAMS):
>
> .PHONY: check-norun
> check-norun: $(check_PROGRAMS)
>
> and type `
Hello,
I'm using AUTOMAKE_OPTIONS = dejagnu with automake 1.7.9 and I want to
build check_PROGRAMS without executing them. Is it possible?
I've looked into the generated Makefile, the rule seems to be
check-am: all-am
$(MAKE) $(AM_MAKEFLAGS) $(check_PROGRAMS)
$(MAKE) $(AM_MAKEFLA
Hello Bob,
On Tue, Jun 28, 2005 at 09:45:42AM -0600, Bob Proulx wrote:
> In the message headers is included this information:
Thanks!
With kind regards,
Baurzhan.
On Tue, Jun 28, 2005 at 06:31:57PM +0200, Ralf Wildenhues wrote:
> Hmm. I don't know whether AC_CONFIG_SUBDIRS can give you the
> flexibility you want here. If you unconditionally build both packages,
> there is no need to check for libl1 during src1/configure.
The problem is, I have to check th
Hello Ralf,
[This thread was started on Jun 7. I couldn't find the list archive --
http://directory.fsf.org/GNU/automake.html doesn't mention any, and
http://sources.redhat.com/ml/automake/2005-06/ says there were no
messages sent this month. Which archive do you use?]
On Tue, Jun 07, 2005 at 04:
Hello Ralf,
thanks for your prompt answer!
On Tue, Jun 07, 2005 at 04:16:26PM +0200, Ralf Wildenhues wrote:
> Put
> AC_CONFIG_SUBDIRS([d1 d2 l1 l2 src1 src2])
> in toplevel configure.ac and
> SUBDIRS = d1 d2 l1 l2 src1 src2
> in toplevel Makefile.am, in the order in which you want them config
Hello,
some time ago I asked a question on how to specify directory
dependencies. At that time I solved the problem by leaving just the
top-level Makefile.am and building all targets (binaries, libraries,
test programs) from it. In this way, I could specify explicit
dependencies between the binari
On Fri, Mar 11, 2005 at 12:31:06PM +0100, Ralf Wildenhues wrote:
> > One more question: how do I define that "make" alone should build zzz,
> > and test1..testn should be built only when I do "make check"?
>
> Put them in check_PROGRAMS.
Wow, now I have Makefile.am exactly as I want it! Thanks mu
On Mon, Mar 07, 2005 at 04:49:11PM +0100, Stepan Kasal wrote:
> for each AC_SUBSTed variable, automake adds a line like
>
> ZZZ_LIBS = @ZZZ_LIBS@
>
> so there is generally no need to use the @...@ notation in Makefile.am.
Yes, thanks for the info! I've replaced all @...@ references with
$(
44 matches
Mail list logo
