Noah Neumark

Is min-devkit still being developed? I think I read that the guy running that project no longer works at Cycling. Following the instructions on Github for creating a new project, then running cmake commands, I get errors for missing files. Is the package manager approach going to go back online? The one available there is the old .57 version, while github is .60.

Is min-devkit still being developed? I think I read that the guy running that project no longer works at Cycling. Following the instructions

min_devkit-support

I can reproduce issues creating projects with the scripts when using the 0.6.0 release download due to some missing files, and we will look into fixing this. 

However you should have no issues with these scripts if you instead clone the repository, e.g.:

git clone https://github.com/Cycling74/min-devkit.git --recursive

From here you should be able to make projects and packages by running the package creation script:

ruby script/create_package.rb ../foopackage

please let me know if that doesn't get you going.

I can reproduce issues creating projects with the scripts when using the 0.6.0 release download due to some missing files, and we will look into fixing this. 

However you should have no issues with these scripts if you instead clone the repository, e.g.:
cd ~/Max 8/Packages
git clone https://github.com/Cycling74/min-devkit.git --recursive
From here you should be able to make projects and packages by running the package creation script:
cd min-devkit
ruby script/create_package.rb ../foopackage

and then follow the instructions here for creating a new object.

I did follow all those instructions and I started from a git clone. I get the missing files error when I try to cmake build from the package I created using the ruby script.

aha, I see what is missing now. due to a recent minor change in our cmake scripts there is now a requirement to update all sub-modules after running the package creation script. I will update the package script to fix this for a future release, but for now you simply need to run 

 from your new package folder after running the script. The steps should be something like:

from here you can follow the step in the document - 

https://github.com/Cycling74/min-devkit/blob/main/HowTo-NewObject.md

aha, I see what is missing now. due to a recent minor change in our cmake scripts there is now a requirement to update all sub-modules after running the package creation script. I will update the package script to fix this for a future release, but for now you simply need to run git submodule update --init --recursive from your new package folder after running the script. The steps should be something like:

cd ~/Documents/Max 8/Packages/min-devkit
ruby script/create_package.rb ../mypackage
cd ../mypackage
git submodule update --init --recursive

from here you can follow the step in the document - https://github.com/Cycling74/min-devkit/blob/main/HowTo-NewObject.md 

Min_devkit support