On May 28, 2015, at 7:52 PM, Djimeli Konrad <djkonr...@gmail.com> wrote:

> I have  successfully generated a shared library from src/lib of the FreeWRL 
> source code with cmake, giving me the ability to compile FreeWRL without most 
> of its dependencies but so far it still depends on opengl and libxml. Given 
> that some parts of the parser uses GL defined types, I would have to define 
> those types in an external file and add to the source code to resolve this 
> dependency but since the FreeWRL X3D parser depends on libxml, I am not 
> certain if a solution to this would be to add the libxml to src/others of the 
> BRLCAD source code or to set the compilation of the X3D importer I would be 
> developing as optional.

When and if the X3D importer gets to a “finished” production-viable state while 
requiring FreeWRL, then we will formally incorporate it (and its libxml2 
dependency) as a fully managed dependency in src/other.  Until then, it can 
simply detect it as a system library and enable compilation optionally if/when 
detected.

> I am presently testing the generated library and I am facing some issues with 
> threads, so I would like to take a day or two to learn more about the FreeWRL 
> thread implementation in order to resolve the issues.

Ugh.  I didn’t know that it was multithreaded.  Looking through the dev 
history, it looks like the author used it as a fun learning exercise.  Still, 
can you explain what the issues are in more detail?  If it’s properly 
encapsulated, it shouldn’t matter (to you) that it’s multithreaded.

Cheers!
Sean


------------------------------------------------------------------------------
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to