This forums is for OS project announcements including project openings, new releases, update notices, test requests, and job openings (both paying and volunteer).
Any feedback is very welcome. If you want to participate in the development, found bugs or have any questions, tell me about them here or contact me at [email protected].
2.x did break my existing scripts, and the documentation is a bit sparse (especially since I needed to fix some things, like targets), but otherwise great job!
Also, you finally have a proper domain (:
Sorry for breaking your scripts, but okay it's a major release, and I at least didn't change the entire syntax (and I will not, don't worry)
I made the specialization statements (like "system windows"/"architecture x123") more generalized with "on system windows" etc. so it is easier to add custom specialization conditions when using the interpreter library in a third-party program. Also the parser is now more strict to some specific errors.
Happy to hear that you can make good use from it, I'll keep this thread up-to-date with further updates.
Haha, breaking changes are always expected with a major release. Thankfully it didn't break too much.
One thing though, the error reporting might either be borked, or could be improved -- it would be nice to know which file the error occurred in.
I had an old Utilities.capri script, that I forgot to take into account -- I didn't "import File;", so it was erroring on that thing -- I spent a good 5 minutes trying to figure it out before realising it wasn't in my actual script...
eryjus wrote:I see the source available for browsing on the official site, but do you have the source hosted on GitHub or something similar?
Hey eryjus,
it is currently not publicly hosted on one of these sites. You can obtain the sources from the distribution archives.
If you want to contribute at the moment, feel free to send me patches
muazzam wrote:How can you say that it is better than Makefiles, build scripts or others? Can you write about it on your website (that why is Capri better)?
Hey muazzam,
I never said that it is better than make & other build scripts, but it is a proper alternative. It's easily portable with no 3rd-party dependencies, the scripts are write-once-run-everywhere (as far as you can reconcile your filesystem scripting) and you can do much more complex tasks with simpler code than you could ever do with makefiles. It is also built in modules and extendable with low effort, so you can not only use it as a build script, but also as for example your operating systems command interpreter.
Roman wrote:
cp: ../capri-cli/native/io.so: No such file or directory
...and some other similar errors.
Hello Roman,
what exactly did you do, on what system? I'm always trying to make the build scripts as portable as possible, but it's not easy to cover every possible combination of environments
MacBook-Pro-Roman:capri-cli roman$ ./build.sh all install
OS X Yosemite 10.10.3.
I've got to warn you, Apple screwed something up with 10.10.3 and the accompanying Xcode 6.3 + Command Line Tools.
I installed CLT 6.2 to get around some issues, perhaps you can try that?
MacBook-Pro-Roman:capri-cli roman$ ./build.sh all install
OS X Yosemite 10.10.3.
I've got to warn you, Apple screwed something up with 10.10.3 and the accompanying Xcode 6.3 + Command Line Tools.
I installed CLT 6.2 to get around some issues, perhaps you can try that?
Possibly a problem with this; also, what shell are you using? The scripts are made for bash.
MacBook-Pro-Roman:capri-cli roman$ ./build.sh all install
OS X Yosemite 10.10.3.
I've got to warn you, Apple screwed something up with 10.10.3 and the accompanying Xcode 6.3 + Command Line Tools.
I installed CLT 6.2 to get around some issues, perhaps you can try that?
Possibly a problem with this; also, what shell are you using? The scripts are made for bash.
(and I will not, don't worry)
