On a related note, does the restriction of not using shell functions in
autoconf macros still remain, or have the OSs with such shells now gone
the way of SunOS 4.x?
Cheers,
Alex.
--
Alex Hornby <[EMAIL PROTECTED]>
On Thu, 2002-08-29 at 10:57, Akim Demaille wrote:
>
> | There are compilers which don't accept `.cc' but need `.cpp' for C++
> | files. Among them are z/OS (by default) and various compilers for
> | MS-DOS and Windows. What about support for a CXXEXT variable? It is
> | quite easy to add a rul
Richard Stallman writes:
>
> I think we need to ask the community of developers what they would
> think of this change. It sounds good, but it could have pitfalls
> we have not thought of.
>
> Would someone like to do that?
I dislike the idea of this kind of hard coding. I'd much rather
A generic CORBA wrapper is going to be complicated. Here's my 2p
worth. This may be more appropriate to automake than autoconf...
Ruslan Shevchenko writes:
> 1. different ORB use different extensions.
>
> what mean .idl_c.hh : idl 2 c and hh ?
>can it be somethin like:
> id
Ruslan Shevchenko writes:
> Are exists some documentation online ?
> How it determinate the name and number of generated source files ?
>
It takes them as environment variables. For example here is one of my
my TAO rules.
.idl_c.hh:
source='$<' object='$*_c.hh $*_s.hh $*_c.cpp $*_s.c
Diego Sevilla Ruiz ([EMAIL PROTECTED]) writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all:
>
> Sorry for my ignorance... but what is depcomp? I've downloaded the latest
>autoconf
> release and I don't find it. I can't find it in the autoconf's documentation. Help,
Ruslan,
I think you will find that automake's depcomp in C preprocessor mode
already handles IDL dependencies (I'm using the CVS version now :).
Regards,
Alex.
Ruslan Shevchenko writes:
> 1. I think it's also must be somewhere near my CORBA macroses. (hmm,
> may be really create separate pag
AFAIK .cpp is the most portable C++ extension. The Mozilla and ACE (hi
Ossama:) people settled on it for that reason.
It is something akin to slow torture to get VC++ using .cc (requires
registry mangling etc). BCB 4 won't use .cc at all.
Alex.
Lars J. Aas writes:
> On Wed, Jul 19, 2000 at 0
As IDL files use standard C preprocessor syntax for dependent
inclusion, is it not possible to wrap the idl compile in depcomp?
My IDL build rules are already structured as suffix rules, with a
small wrapper script around the IDL compiler that uses lockfile(1) to
prevent two targets (e.g. client
Akim Demaille writes:
>
> If there is a means to have this cleaner, please do it, I don't know
> what to do (or are you saying I should `cvs update -d', then cvs
> remove depth first?).
>
> Akim
Akim,
The cleanest way to do this is to have a ~/.cvsrc containing:
update -P -d
chec
Does anyone have a pure 4.3BSD system connected up to the net? If so
why not give the doubters a guest account so that they can see for
themselves.
Perhaps an ls -l and uname -a of such a machine would be equally
satisfactory?
Alex.
The libodbc++ project has a similar problem. They solve it by
installing odbc++/config.h with rewritten macro
names like ODBCXX_HAVE_FOO.
The rule looks like this:
config.h: $(CONFIG_HEADER) config.h.in
cat $(srcdir)/config.h.in > $@
sed -e 's/#\([^ ][^ ]*\) \([^ ][^ ]*\)/#\1 OD
I don't think we need to get carried away on this.
Why not start with the 90% solution start that just packages the
binaries together with a manifest ( which I would hope is the lowest
common denominator of package systems ).
Once that is accomplished, then you can start worrying about
rc file
13 matches
Mail list logo
