On Mon, Sep 14, 2015 at 10:54:53AM +0200, aitor_czr wrote:
> Hi Katolaz,
>
> I tried it but it doesn't work:
>
> aitor@gnuinos:~/netman/backend_src/src$ gcc -g -I../include
Try with the actual path to the include. With a -I option it isn't clear what home
directory the -I is relative to.
I remember a long discussion online about the "home" directory from which include
paths started indicating that they should be relative to the source file doing the
include, not to the home directory where the compiler was invoked. I don't know
what the final decision was.
But is you do provide an absolute path in the -I and it works, you'll know for sure
that there was a problem with the "../".
-- hendrik
> core_functions.c
file_functions.c backend.c essid_encoder.c -o
> backend
> core_functions.c:29:36: fatal error: include/core_functions.h: No
> existe el fichero o el directorio
> #include "include/core_functions.h"
> ^
> compilation terminated.
> file_functions.c:26:27: fatal error: include/paths.h: No existe el
> fichero o el directorio
> #include "include/paths.h"
> ^
> compilation terminated.
> backend.c:28:36: fatal error: include/core_functions.h: No existe el
> fichero o el directorio
> #include "include/core_functions.h"
> ^
> compilation terminated.
> essid_encoder.c:50:35: fatal error: include/essid_encoder.h: No
> existe el fichero o el directorio
> #include "include/essid_encoder.h"
> ^
> compilation terminated.
>
> Aitor.
>
> On 14/09/15 10:39, KatolaZ wrote:
> >I think you guys must rather specify an appropriate "-I" flag to gcc
> >in the Makefile. I have never ever seen "../something" in an
> >#include....
> >
> >My2Cents
> >
> >KatolaZ
>
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
::
[DNG] where to find include files.
