This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [4.5] [RFC] Move line-map.* to its own library (libloc)

From: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
To: Manuel López-Ibáñez <lopezibanez at gmail dot com>, Gcc Patch List <gcc-patches at gcc dot gnu dot org>, Tom Tromey <tromey at redhat dot com>
Date: Tue, 18 Nov 2008 08:01:28 +0100
Subject: Re: [4.5] [RFC] Move line-map.* to its own library (libloc)
References: <6c33472e0811141202n1619d35n6d7929768e3e36bf@mail.gmail.com> <20081115093943.GA11639@ins.uni-bonn.de> <6c33472e0811171514m3beb39acpc38b684d9a643a5@mail.gmail.com> <20081118064945.GA5172@ins.uni-bonn.de>

BTW, even with the desire/need to separate the code into its own
library, I completely fail to see why it needs to be in a separate
directory, with a separate configure script and separate makefile.

You don't do such things below gcc/, and they are certainly not
required from the build system.  And IIUC you are not going to use
libloc as a stand-along library (i.e., independent of GCC) anyway,
right?

Cheers,
Ralf

Follow-Ups:
- Re: [4.5] [RFC] Move line-map.* to its own library (libloc)
  - From: Manuel López-Ibáñez

References:
- [4.5] [RFC] Move line-map.* to its own library (libloc)
  - From: Manuel López-Ibáñez
- Re: [4.5] [RFC] Move line-map.* to its own library (libloc)
  - From: Ralf Wildenhues
- Re: [4.5] [RFC] Move line-map.* to its own library (libloc)
  - From: Manuel López-Ibáñez
- Re: [4.5] [RFC] Move line-map.* to its own library (libloc)
  - From: Ralf Wildenhues

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]