On Tue, 7 May 2013, Thorsten Schöning wrote:
> Is there any interest in project files to ship with PCRE? Other
> projects do so in e.g. contrib folders, even if they don't officially
> support them, just in case anybody finds them to be of any help. I
> could provide projects for C++ Builder 5, 6 and XE 3.
PCRE does have a Contrib directory on the FTP site, where various bits
and pieces have been put. I could easily add files there.
> Another approach I successfully used for some years with BCB 5 and 6
> was to make sure that include and library paths of PCRE are configured
> before the default paths of the IDE in the dialogs where one can
> manage those paths. Afterwards one can open the project files using a
> text editor and manually add the self created library for pcre itself,
> pcrecpp doesn't ship with the IDE, in the library nodes where the IDE
> manages it's own libraries to link against in front of the IDE-own
> libraries. This way one can use the default PCRE function names
> without getting access violations on runtime.
>
> <ALLLIB value="libpcre.lib $(LIBFILES) $(LIBRARIES) import32.lib cp32mt.lib"/>
That looks like a useful note that could be included somewhere in the
documentation, if you are agreeable. (I'm afraid I don't understand any
of this Windows-related stuff, as I am a Linux user only.)
Philip
--
Philip Hazel
