Propellent library path
Hanno
Posts: 1,130
Hi,
I'm trying to simplify include file management for 12Blocks and ViewPort.
Currently spin file can only specify the filename of required objects- no relative/absolute paths.
To find files, Propellent/Propeller Tool first looks in the "top" file directory and then one "library" directory. Many objects rely on the files shared by the Propeller Tool library- so this library must be included.
My tools come with objects like "conduit" that must be included in the users code. Currently, I do not place these objects into the Propeller Tool library. Instead, they clutter up the directory of "user" files. Especially for 12Blocks, I would like to fix this by:
When ViewPort/12Blocks start up, they use propellent to discover the current library directory. They then verify that required library files are up to date in the Propeller Tool Library. If they're not, they copy them there and warn if name collisions occur. This would let users compile files with my tools, any other tool, and the Propeller Tool. It would keep just the user's files in the user directory.
Another option would be for the Propeller Tool/Propellent/other tools to support multiple include directories- this is how most other IDE's do it...
Hanno
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Download a free trial of ViewPort- the premier visual debugger for the Propeller
Includes full debugger, simulated instruments, fuzzy logic, and OpenCV for computer vision. Now a Parallax Product!
I'm trying to simplify include file management for 12Blocks and ViewPort.
Currently spin file can only specify the filename of required objects- no relative/absolute paths.
To find files, Propellent/Propeller Tool first looks in the "top" file directory and then one "library" directory. Many objects rely on the files shared by the Propeller Tool library- so this library must be included.
My tools come with objects like "conduit" that must be included in the users code. Currently, I do not place these objects into the Propeller Tool library. Instead, they clutter up the directory of "user" files. Especially for 12Blocks, I would like to fix this by:
When ViewPort/12Blocks start up, they use propellent to discover the current library directory. They then verify that required library files are up to date in the Propeller Tool Library. If they're not, they copy them there and warn if name collisions occur. This would let users compile files with my tools, any other tool, and the Propeller Tool. It would keep just the user's files in the user directory.
Another option would be for the Propeller Tool/Propellent/other tools to support multiple include directories- this is how most other IDE's do it...
Hanno
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Download a free trial of ViewPort- the premier visual debugger for the Propeller
Includes full debugger, simulated instruments, fuzzy logic, and OpenCV for computer vision. Now a Parallax Product!
Comments
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Cheers,
Simon
www.norfolkhelicopterclub.com
Announcement: To cut costs in the current economic climate, we have switched-off the light at the end of the tunnel.