Yes Michael, good catch!

You are a CMake expert in 10 minutes.  The same level of expertise in 
autotools would take a person 10 days.

We need to add the includes, like you suggest.  (I missed that in my 
testing because I had my includes in a standard place.)


You can run any CMake built makefile with VERBOSE1= to see the output, 
and then redirect that to a file.


make VERBOSE=1   > output.txt


Dick


Michael Fischer wrote:
> Hello Dick,
>
> I think I found the next problem and solution for it.
>
> I have set the LIBFTDI_INCLUDE_DIR but this variable is not used
> in the CMakeList.txt.
>
> I think you must add this to your include_directories where you
> added all the other directories at the end of the file.
>
> I am not sure, perhapse you should only add the LIBFTDI_INCLUDE_DIR
> in case you use the BUILD_FT2232_LIBFTDI. Here after the
> find_package(LibFTDI)
>
> Is the a trick available to see the output of the make which are currently
> running?
>
> Best regards,
>
> Michael
>
>
>   

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to