Is Crossworks really this bad about finding includes?

Comments

4 comments

  • Avatar
    Michael Johnson

    There's no means to specify a recursive set of directories as an include path. This is a nasty area particularly when ../.. starts to be used. If you generate an IAR/Keil project file you may be able to import this - we're working on importing eclipse .project files.

    0
    Comment actions Permalink
  • Avatar
    Ceculbe

    It just seems kind of odd behavior to me. The .c source files in recursive directories are all included with no problems. The .h files in the same folders are even visible in the project explorer, but not automatically added to the build.

    Wouldn't it be more consistent to automatically include any header files that are shown in the project explorer? Then, if I don't want them in the project, I can use the filter property to exclude them, or I can manually exclude them. 

    0
    Comment actions Permalink
  • Avatar
    kim Pedersen

    Same issue as above with STMCubeMx.

    Is there an easy way to include files ?

    0
    Comment actions Permalink
  • Avatar
    JJ

    I ran across the same issue. You can setup global macros for each of the include paths. (pulldown menu: Project > Macros) 

    Create a unique macro for each path.

    0
    Comment actions Permalink

Please sign in to leave a comment.