I tried doing an out of source build of this library but it did not work. I created a patch that fixes the issue. Please take a look at: 464128.bugs.gentoo.org...
can anybody help me building libconfig with MinGW under Windows and without Cygwin??
It seems like defining make LDFLAGS='foo' only gets applied to the C library and not the C++ one, should this be defined somewhere else or is it just a bug?
Hi, I'm looking into using libconfig++ and in some regards it looks great
* Good documentation
* Nice format (at least compared to the limits of INI and eyesore of XML :)
* Convenient methods (I was looking into Boost property trees, and found myself wanting to write a a very libconfig-esque abstraction layer on top :)
I do have a few gripes with it though:
* I'm wanting to add methods to the libconfig::Setting class, however, since the constructor for this one is private, it looks tricky. It's noted down in the header as not supported(?), is this likely to change?
* The way that libconfig::Setting must be initialised with a reference appears to make it again very clunky to wrap around, it pretty much disables any abstraction class exposing a libconfig::Setting object, right? Why?
really nice library. however:
- the Setting class is missing all the simple "lookup()" function (with the same semantic than the ones in the Config class).
- the readFile() and writeFile method are missing an overload taking a std::string for the file name.
- for @include directives: included files should be specified relative to the directory of the including file (not the current directory)
mesmerism, I made a config viewer that uses your library. If you want more info, pm me.
Of course, this library is highly reccomendated.
Sorry about my english.
Hi! Fantastic Library! Thank you very much!
However, i always have had a problem with Visual Studio building.
tests.c(25): fatal error C1083: Cannot open include file: 'unistd.h': No such file or directory
I workaround this problem commenting fully test.c (Sigh!) . Not the ideal solution...
Any idea? Thanks!
Sorry for my English
mesmerism, when i use complex configs with a complex depth than 3, it's almost neccesary to use "hacks" to access the string (...value.sval) rather tan config_setting_lookup_string because the double pointer mess up a lot, in my case.
Keep working, this library pwns ;)
Nomasvisto, why do you need "hacks" to access string values? Just assign the Setting object to a std::string or const char *.
It would be very helpful to use a libconfig in c++ that it wouldn't be a c++ wrapper from the c library, I'm sure you will increase people who help you easily and you will gain more people in the proyect.
I made a lot of times use of hacks to access to strings in complex configs (NameSettingWhatever->value.sval, something like that), with complexity superior of 3 (list of lists of arrays, for example)
Even with their bad points, I reccomend it!
A massive parallel-processing computing platform that solves big data problems.
A Wiki-like text processor.