https://opensource.cit-ec.de/https://opensource.cit-ec.de/favicon.ico?14265323552012-01-06T17:20:42ZResearch for Cognitive InteractionOpenKC - Bug #27: OpenKC doesn`t find FRI headershttps://opensource.cit-ec.de/issues/27?journal_id=202012-01-06T17:20:42ZArne Nordmannanordman@cor-lab.uni-bielefeld.de
<ul></ul><p>Adding</p>
<pre><code>CPPFLAGS="$CPPFLAGS -I$includedir"</code></pre>
<p>to configure.ac did the trick for me, because it tells <code>AC_CHECK_HEADER</code> to also search inside <code>$includedir</code>.</p> OpenKC - Bug #27: OpenKC doesn`t find FRI headershttps://opensource.cit-ec.de/issues/27?journal_id=212012-01-13T15:12:46ZMatthias Schöpfermschoepf@techfak.uni-bielefeld.de
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul><p>Hi Arne!</p>
<p>README.TXT says:</p>
<p>"Remember to export CPPFLAGS=-I/path/to/fricomm.h. This file comes as<br />part of FRI and cannot be included into OpenKC because of copyright<br />issues."</p>
<p>Did this not do the job for you?! If so, please respond and I will see if I can add an option to configure, where the location of fricomm.h can be passed to the autotools-chain.</p>
<p>Regards!</p> OpenKC - Bug #27: OpenKC doesn`t find FRI headershttps://opensource.cit-ec.de/issues/27?journal_id=222012-01-16T12:47:16ZArne Nordmannanordman@cor-lab.uni-bielefeld.de
<ul></ul><p>Yes, that works! Sorry, that I missed this hint in the README.txt.</p>
<p>Maybe it is more convenient though, If you add</p>
<pre><code>CPPFLAGS="$CPPFLAGS -I$includedir"</code></pre>
<p>to the configure.ac file, so that you can just type</p>
<pre><code>./configure --includedir=/path/to/fricomm.h</code></pre>
<p>and the CPPFLAGS stuff is done for you (and this is a more common command line argument I guess).<br />Anyway ... it works. Thanks very much.</p>