Is Crossworks really this bad about finding includes?

Follow

Ceculbe

• April 03, 2018 04:18

Yeah, there's a little frustration there. I'm trying to use some of the STM32Cube resources, which is a headache enough, but Crossworks isn't helping.

The STM32Cube directories have source and header files in folders that are nested multiple levels deep. Dropping those folders into a Crossworks project (as dynamic folders) seems to pick up all the multiple levels of .c files. However, do I really have to manually add each of the folders with header files to the user include path? Even the project root folder? And do those paths really not include subdirectories? 

At this rate, I'll be chasing missing includes for hours. If I'm a fool and just missing something simple, that would be great. If not, why in the world is Crossworks set up like this?

0

• 

  Michael Johnson

  • April 03, 2018 10:55

  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
• 

  Ceculbe

  • April 03, 2018 19:04

  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
• 

  kim Pedersen

  • May 07, 2018 10:51

  Same issue as above with STMCubeMx.

  Is there an easy way to include files ?

  0

  Comment actions Permalink
• 

  JJ

  • September 18, 2018 20:18

  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.