Search Results
Search results 81-100 of 175.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Quote from mackella001: “the SDK ” What SDK ? Quote from mackella001: “when i just copy the "ses" directory to a new working directory all of the folders/code cannot be located for opening ” A file copy does not modify the contents of the file. So, if your project contains relative paths, you will have to copy it to a place which is still at the same relative location for those paths to work! That applies to any use of relative paths - not just SES,
-
I don't see that option in v3.40 - is it quite recent?
-
Quote from SEGGER - Nino: “We will add your proposal to our feature wish list and see if this could be added in future so the Always Rebuild option would get additional config options ” Thanks - either as additional options to the existing 'Always Rebuild', or as a separate new setting; eg, 'Include in Every Build'
-
Thanks - that would be great.
-
Aha! So what I really want is to have that option - 'when build required' or 'Always' - available on the "Always (sic) Rebuild" file option! I guess the "Always Rebuild" option could be changed to a "When to Rebuild" option, with 3 settings: 1. As required (default); 2. When any build is required; 3. Always. (could have a 4th option - 'Never' - to replace the separate 'Exclude from build' option and consolidate it all into 1 setting).
-
It is a common requirement to have a build time & date included in the executable. An easy way to do this is to have a file with something like C Source Code (2 lines)But, for that to work, it has to be re-compiled every time the project is rebuilt. SES has an 'Always Rebuild' option - but this will cause the affected file(s) to be rebuilt even when there is no other reason to build. Which is not quite what we want! So what I'm looking for is an option to compile a file every time anything else …
-
In the standalone RTT Viewer, it is possible to set it to record to a file. Is this possible for the 'Debug Terminal' Window inside SES ? If so, how?
-
Quote from teddy_ziyu: “but now the error message shows " Unable to open include file 'lint_cppmac.h' [-e322] " ” So have you looked up that error code in the PC Lint documentation to see if it gives more details, and/or suggestions on how to resolve it ? Obvious first steps whenever any tool tells you it can't open a file: 1. Does that file actually exist at all? 2. If it does exist, is it in a location where the tool will find it? 3. Can you open it using any other tool; eg, Notepad?
-
Cross-post: devzone.nordicsemi.com/f/nordi…gger-to-do-misra-checking