[redland-dev] storage confusion

[Lauri Aalto]

Hi,

try "make example1.exe" instead to get the correct compiler flags on cygwin.

LIBRDF_INTERNAL is a flag used when building the librdf library
itself. It includes all the *_internal.h headers which contain e.g.
internal struct definitions while the non-internal headers just
contain opaque typedefs. It shouldn't be used with modules like the
examples which merely use the library API.

sqlite3 storage probably suits your needs if your data size is
kilostatements at most. The storage works but is not very optimised.

Lauri

On Wed, Mar 18, 2009 at 6:09 PM, Gregg Reynolds <dev at mobileink.com> wrote:
> I managed to get redland to compile on cygwin with sqlite3 support,
> but the examples won't build:
>
> $ make example1
> gcc -DLIBRDF_INTERNAL=1 -g -O2    example1.c   -o example1
> In file included from /usr/local/include/redland.h:40,
>                 from example1.c:30:
> /usr/local/include/librdf.h:266:26: rdf_internal.h: No such file or directory
>
> etc.  Questions:
>
> - What's this LIBRDF_INTERNAL?
>
> - example1 uses "storage=librdf_new_storage(world, "memory", "test",
> NULL);", so I assume the problem is not the lack of bdb support (as
> section 3 of the build/install webpage warns of possible problems in
> that case).  (Docs seem to be a bit out of sync)
>
> - should I just use the bdb storage instead of sqlite3?  Eventually
> I'm going to want to package up a standalone app that might see
> triples in the small 100's of thousands at most.
>
> Thanks,
>
> gregg
> _______________________________________________
> redland-dev mailing list
> redland-dev at lists.librdf.org
> http://lists.librdf.org/mailman/listinfo/redland-dev
>