Date: Fri, 2 Jul 2010 16:05:28 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: Philip Herron <redbrain@gcc.gnu.org> Cc: freebsd-hackers@freebsd.org, Matthew Fleming <mdf356@gmail.com> Subject: Re: Using lex in a shared library Message-ID: <AANLkTiliDSkkuwN4FpJdzIxALp_Xzbx4ac0MCa31W85j@mail.gmail.com> In-Reply-To: <AANLkTintFOTV_FztqxIVE2d1PI15qIgoljA3_aOPWUGb@mail.gmail.com> References: <AANLkTilp0zvMRbw96cifhIzmT4YbNVkxgOFZFa_nvl2m@mail.gmail.com> <AANLkTildN27EcRSXXTpQl5vZD-kczKrIbgERQuiNkiTt@mail.gmail.com> <AANLkTik1dsTJYw0jy5mfEljWe-ETH1RJlZ8S4-taV1PV@mail.gmail.com> <AANLkTintFOTV_FztqxIVE2d1PI15qIgoljA3_aOPWUGb@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 2, 2010 at 3:53 PM, Philip Herron <redbrain@gcc.gnu.org> wrote: > On 2 July 2010 23:31, Matthew Fleming <mdf356@gmail.com> wrote: >> On Fri, Jul 2, 2010 at 2:54 PM, Philip Herron <redbrain@gcc.gnu.org> wro= te: >>> Although maybe not helpful but have you considered using >>> automake/libtool instead makes it so much simpler in my opinion. >> >> Instead of... ? =A0Instead of this makefile? > > Yeah to create your self a shared library using automake: ... > This will generate you all the Makefie.in files recursively over your > work dir. When building these Makefile.in you only need do it once > really, unless you change your makefile.am files. The makefiles.in are > designed to be portable. All they need is some configuration though > autoconf to tell it what compiler to use etc. Why create a dependency on several ports (which tends to be painful to maintain) instead of using what's available to you in the base system? Thanks, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTiliDSkkuwN4FpJdzIxALp_Xzbx4ac0MCa31W85j>