You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One issue that is quite an annoyance with the text-based startup file is that it lists the fully-qualified file name, including extension. The issue is that the extension varies from system to system, so when I build with e.g. SIMULATION=native the extensions need to be .so, but when building for RTEMS it needs to be .obj.
Ideally I'd like to see a solution that only lists the basename of the app file in the user-maintained source file, and the extra info, in particular the extension, is attached by the build system based on the file type of loadable modules for the particular platform you are building.
However the first step to any of this would be to get this table-based change in place, then smarter translation on the build side could be a follow-on.
One issue that is quite an annoyance with the text-based startup file is that it lists the fully-qualified file name, including extension. The issue is that the extension varies from system to system, so when I build with e.g.
SIMULATION=native
the extensions need to be.so
, but when building for RTEMS it needs to be.obj
.Ideally I'd like to see a solution that only lists the basename of the app file in the user-maintained source file, and the extra info, in particular the extension, is attached by the build system based on the file type of loadable modules for the particular platform you are building.
However the first step to any of this would be to get this table-based change in place, then smarter translation on the build side could be a follow-on.
Originally posted by @jphickey in #588 (comment)
The text was updated successfully, but these errors were encountered: