OK, maybe my first message was too general and too aggressive.
I used multiple argument files at the following way:
1 file for +define and other compiler directives (-mfcu…)
1 file for +incdir+ directives
1 file for parsing file-list
For some reason, this didn’t count the incdirs properly.
Fixed by creating a single file:
-f file1.f
-f file2.f
-f file3.f
Which worked..
Thanks,
Tomer
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Tomer,
SVEditor treats each top-level argument file as independent, from a parsing perspective. So, in your example, SVEditor will not consider the defines or include paths specified by file1.f and file2.f when parsing the files from file3.f
SVEditor does look at all content contributed by all top-level argument files when doing content assist or navigation.
Your approach of composing a top-level argument file with multiple -f lines is correct.
I'm going to close this issue, since it appears SVEditor is working as designed.
Best Regards,
Matthew
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have this working on my end (1.8.3). In my project only have 2 files.f's... not sure if >2 work.
What symptoms are you seeing?
OK, maybe my first message was too general and too aggressive.
I used multiple argument files at the following way:
1 file for +define and other compiler directives (-mfcu…)
1 file for +incdir+ directives
1 file for parsing file-list
For some reason, this didn’t count the incdirs properly.
Fixed by creating a single file:
-f file1.f
-f file2.f
-f file3.f
Which worked..
Thanks,
Tomer
Hi Tomer,
SVEditor treats each top-level argument file as independent, from a parsing perspective. So, in your example, SVEditor will not consider the defines or include paths specified by file1.f and file2.f when parsing the files from file3.f
SVEditor does look at all content contributed by all top-level argument files when doing content assist or navigation.
Your approach of composing a top-level argument file with multiple -f lines is correct.
Best Regards,
Matthew
Thanks for the clear and informative answer.
Tomer