Oliver Hartkopp wrote: > Wolfgang Grandegger wrote: >> Oliver Hartkopp wrote: > >>> I remember, why we had two separate paths containing nearly the same stuff: >> We separated them to avoid conflicts with the *almost* similar kernel >> include files and that works well. You can disable CAN support in the >> kernel config and build all modules from BerliOS without any trouble. As >> a consequence, we can develop and test now new interfaces (touching the >> header files) without kernel interference. >> >>> All of these include file are including other includes files in the same >>> include paths. So a symlink nor your #include approach will help us here :-( >> My approach did work fine with the can-utils. > > Ah, i see. > > As we use > > KERNELDIR = ../kernel/2.6 > > and > > -I$(KERNELDIR)/include > > both 'linux' and 'socketcan' can be resolved properly, right? > > If so, please go ahead with your idea
I have just commited my changes. Please check. Wolfgang. _______________________________________________ Socketcan-core mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-core
