Skip to content

Docs corrections #22

@turuluu

Description

@turuluu

iPlug2OOS seems like a good starting point also for non-containerized workflow. I've not used claude or other LLMs with this, so I also haven't looked if the main point of the containerization is to have sandboxing for the GenAI-code-systems. However I got my old project refactored using it so I can use clion with cmake. Here's a few things I noted on the way.

In the docs guide, these arguments are wrong:
./duplicate.py PROJECT_NAME MANUFACTURER_NAME

Usage is:
Usage: duplicate.py inputprojectname outputprojectname manufacturername (outputprojectpath)

So it should be:
./duplicate.py TemplateProject PROJECT_NAME MANUFACTURER_NAME

In case someone tries to use this as a starting point for non-containerized plug-in environment, it might trip them that the iPlug submodule is cloned recursively, but its dependencies aren't. This can be done from the root of iPlug2OOS using:
./setup_container.sh

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions