Desarrollos en Internet - Desarrollador freelance

Que tal! Mi nombre es Hernan y me dedico al desarrollo de sitios webs para empresas o particulares. Si usted tiene una empresa y desea estar en internet le aseguro que con mi equipo creativo su sitio impactara al publico. Hago desarrollos de alto impacto corporativo. Formato cine!! Multimedia i

Re: make dist and sources in subdirs

- Original Message - From: "Robert Collins" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 03, 2001 11:46 PM Subject: make dist and sources in subdirs > I have three questions: > > 1) Based on a recent comment on this list, > I have > > noinst_LIBRARIES = libfoo.a > lib

Re: make dist and BUILT_SOURCES

- Original Message - From: "Akim Demaille" <[EMAIL PROTECTED]> To: "Robert Collins" <[EMAIL PROTECTED]> Subject: Re: make dist and BUILT_SOURCES > > "Robert" == Robert Collins <[EMAIL PROTECTED]> writes: > > Robert> Yet another question from the newbie. I have a number of > Robert>

Errors during autoamake

Hello, I am using gnu tools to configure my build environment. If I run automake --foreign --include-deps I get an error "automake: no `Makefile.am' found or specified" eventhough I have Makefile.am. I have looked at automake doc but did'nt got any macro to set the path for Makefile.am What is

Re: Compiling different extensions based on packages

> "Lars" == Lars von Wedel <[EMAIL PROTECTED]> writes: Lars> How would these best be taken into account in Lars> configure.in/Makefile.am? See the node `The top-level `Makefile.am´ in the doc.

Re: make dist and sources in subdirs

> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: Alexandre> On Apr 3, 2001, "Robert Collins" Alexandre> <[EMAIL PROTECTED]> wrote: >> Is it expected behaviour for a.o,b.o ans c.o from the above example >> to be created in ., or in foo/ ? Alexandre> Yep (Alexandre means `yes, in

Re: make dist and BUILT_SOURCES

> "Robert" == Robert Collins <[EMAIL PROTECTED]> writes: Robert> Yet another question from the newbie. I have a number of Robert> built source (.h and .c) files that are built from other Robert> sources/configure settings. Such as? Robert> "make dist" is failing to find these files. (Some

Re: Problem with EXTRA_*_SOURCES

> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes: Esben> Did you notice the LEX hack ? Am I right about automake Esben> currently lacking support for multiple lexers in one binary? Esben> (although the docs clearly states that it is supported) Lars> I haven't tried the lex support in Auto

Re: make dist and sources in subdirs

On Apr 3, 2001, "Robert Collins" <[EMAIL PROTECTED]> wrote: > Is it expected behaviour for a.o,b.o ans c.o from the above example to > be created in ., or in foo/ ? Yep > It would be good if they could be created in foo/ rather than the > current directory (in case of name collisions. There's

Re: Problem with EXTRA_*_SOURCES

On Wed, Apr 04, 2001 at 02:06:17PM +0200, Esben Haabendal Soerensen wrote: : "Lars J. Aas" <[EMAIL PROTECTED]> writes: : > The below Makefile.am gets rid of the warnings. : : Ah, that makes sense (while the warning message did not so much). : Works nicely also, thanks! You're welcome. : Did you

Re: Problem with EXTRA_*_SOURCES

"Lars J. Aas" <[EMAIL PROTECTED]> writes: > Automake doesn't know about mutually exclusive conditionals (they are > controlled from the configure script, so anything can happen), so you > should rewrite the Makefile.am to something Automake will be more > comfortable with - knowing that a variabl

Re: Problem with EXTRA_*_SOURCES

On Wed, Apr 04, 2001 at 01:40:26PM +0200, Esben Haabendal Soerensen wrote: : I attach the configure.in and src/Makefile.am here. Automake doesn't know about mutually exclusive conditionals (they are controlled from the configure script, so anything can happen), so you should rewrite the Makefile.

Re: Problem with EXTRA_*_SOURCES

"Lars J. Aas" <[EMAIL PROTECTED]> writes: > Then there's probably something weird with your setup of the conditionals. > I'll have to see configure.in and the offending Makefile.am to be able to > assist any further. No problem. The problem is with the PC/SC Lite package from the M.U.S.C.L.E. p

Compiling different extensions based on packages

Hello, I started using automake/autoconf recently and it works out very well. I also developed some macros for external packages (--with-xxx) which are required in our software. Mostly looking at 'examples' in the autoconf macro archive, I found that a useful macro only checks whether something c

Re: Problem with EXTRA_*_SOURCES

On Wed, Apr 04, 2001 at 12:16:35PM +0200, Esben Haabendal Soerensen wrote: : "Lars J. Aas" <[EMAIL PROTECTED]> writes: : > I'm not able to reproduce this behaviour, but I'm using CVS : > Automake. Which version are you using? : : I get the behaviour both with automake 1.4 and CVS version (from t

Re: Problem with EXTRA_*_SOURCES

"Lars J. Aas" <[EMAIL PROTECTED]> writes: > I'm not able to reproduce this behaviour, but I'm using CVS > Automake. Which version are you using? I get the behaviour both with automake 1.4 and CVS version (from today). > Anyways, Automake has been known to not be happy about user > variables co

Re: Problem with EXTRA_*_SOURCES

On Wed, Apr 04, 2001 at 10:31:56AM +0200, Esben Haabendal Soerensen wrote: : "Lars J. Aas" <[EMAIL PROTECTED]> writes: : : > Use an AM_CONDITIONAL instead. : : Thanks, I now have everything working by using AM_CONDITIONAL. I even : got some more understanding of how everything works at the same

Re: Problem with EXTRA_*_SOURCES

"Lars J. Aas" <[EMAIL PROTECTED]> writes: > Use an AM_CONDITIONAL instead. Thanks, I now have everything working by using AM_CONDITIONAL. I even got some more understanding of how everything works at the same time :) Everything works, but... I get a lot (102) warnings like these when I run s