ild -- I personally don't
have the professional version of Visual Studio 2008, which afaict is needed to
do 64-bit builds.) The only change I needed to make in my source code after
adding header and library paths was to add GLOB_NOESCAPE to the flags, in case
productHome contains backslashes.
--
Daniel Schepler
ngw32, and
making sure to use the 64-bit Visual Studio command prompt?
--
Daniel Schepler
On Tuesday, January 03, 2012 09:08:32 PM Bruno Haible wrote:
> Daniel Schepler wrote:
> > First of all, if I try running gnulib-tool --import --lgpl=2 glob, it
> > reports the license of opendir, readdir, closedir modules is
> > incompatible. (I guess because their files
I'm trying to use gnulib sources in order to be able to use glob
internally in the Windows build of our product (i.e. I call
std::string pattern = productHome + "/libraries/*/config/*.xml";
glob(pattern.c_str(), ...);
)
This is using the Debian package of gnulib, which is version
20111211+stabl
