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
Currently by default rossum only builds the main package not its dependencies. you can select to build all the dependencies as well but you have to have them downloaded on your system with an environment variable pointing to the parent library directory. Should this be opposite, in that it defaults to build all the packages and dependencies in a "target" or "build" folder? Where the user can specify if they don't want to build dependencies instead (for quicker debugging purposes). Rust and nodejs do the later, downloading and building all dependencies in the target folder. Setting up a download registry might be a bit out of scope for me, but the dependency web is become an issue, and could be handled better. Can just use git clone calls as well, where rossum just holds a file with library download locations. Would be like
rossum add math
would download math to a temp folder, or into the "target" folder, and automatically link it in the package.json file. ninja, or rossum build would compile the dependency to the "build" or "target" folder. This might take a long time to first build a package, and require a wrapper script or manager script to manage the downloaded dependencies, and to show a progress bar in the console instead of a wall of text from git clone calls.
The text was updated successfully, but these errors were encountered:
Currently by default rossum only builds the main package not its dependencies. you can select to build all the dependencies as well but you have to have them downloaded on your system with an environment variable pointing to the parent library directory. Should this be opposite, in that it defaults to build all the packages and dependencies in a "target" or "build" folder? Where the user can specify if they don't want to build dependencies instead (for quicker debugging purposes). Rust and nodejs do the later, downloading and building all dependencies in the target folder. Setting up a download registry might be a bit out of scope for me, but the dependency web is become an issue, and could be handled better. Can just use
git clone
calls as well, where rossum just holds a file with library download locations. Would be likewould download math to a temp folder, or into the "target" folder, and automatically link it in the package.json file.
ninja
, orrossum build
would compile the dependency to the "build" or "target" folder. This might take a long time to first build a package, and require a wrapper script or manager script to manage the downloaded dependencies, and to show a progress bar in the console instead of a wall of text fromgit clone
calls.The text was updated successfully, but these errors were encountered: