7 hours ago
Hi everyone,
I'm working in a lab environment where the PULP SDK is stored on a read-only NFS share, so I can't modify any files inside the SDK directory. I can only write to my own workspace.
Is there a recommended way to build and run PULP applications without changing the SDK installation itself? For example, can all generated files (build outputs, caches, temporary files, configuration files, etc.) be redirected to a user-defined writable directory through environment variables or build options?
I'd like to keep the shared SDK completely untouched while still being able to compile and run examples. If anyone has experience with this setup, I'd appreciate your advice. Thanks!
I'm working in a lab environment where the PULP SDK is stored on a read-only NFS share, so I can't modify any files inside the SDK directory. I can only write to my own workspace.
Is there a recommended way to build and run PULP applications without changing the SDK installation itself? For example, can all generated files (build outputs, caches, temporary files, configuration files, etc.) be redirected to a user-defined writable directory through environment variables or build options?
I'd like to keep the shared SDK completely untouched while still being able to compile and run examples. If anyone has experience with this setup, I'd appreciate your advice. Thanks!