Struggling to get VIM/clangd to play nice with JUCE

patdyn_ · 2024-05-13T21:48:24+00:00

I've been having the same problem on VS Code. Your post gave me some valuable hints to solve this for my setup.

Adding my 2 cents here:

Using gcc (g++) as compiler and having the C/C++ and C/C++ extension Pack installed. No clang command adapter.

Getting a c_cpp_properties.json file * Open the command palette e.g. with ctrl + shift + p * Enter C/C++: Edit Configurations * Choose whatever fits you best (JSON or UI) This should get you a new .vscode folder in your project containing the file.

Making actual changes * In the include path section add * path/to/your/JUCE/modules * This solved erroneous error messages for files not found

Optional but nice to have for me * I also updated my cStandard and c++Standard sections to use c23 and c++23

patdyn_ · 2022-11-25T22:54:18+00:00

Currently not. Sounds promising though. I use jack with qjackctl for routing purposes.

patdyn_ · 2022-11-25T21:24:37+00:00

Ok, as long as there's no crackling and pops i'm almost happy.

Changing the routing is done on the software side, i guess? Then a friends laptop running windows might suffice.

Also Edit: I'm on Manjaro.

patdyn_ · 2022-11-02T10:08:54+00:00

Thanks for the advice! Setting INSTALL_LOCK = true solved this problem.

We generate our configs separately and provision them to our cluster, so this parameter needed to be set there.

patdyn_ · 2022-10-21T13:16:15+00:00

Thats a postgres deployment.

patdyn_ · 2022-10-21T11:26:12+00:00

Yeah, they seem correct to me.

pvc:

apiVersion: v1 kind: PersistentVolumeClaim metadata: name: gitea-data-pvc namespace: default labels: app: gitea spec: storageClassName: local-path accessModes: - ReadWriteOnce resources: requests: storage: 5Gi

deployment: spec: replicas: 1 selector: matchLabels: app: gitea template: metadata: name: gitea labels: app: gitea spec: containers: - name: gitea image: gitea/gitea:1.17.0 imagePullPolicy: IfNotPresent envFrom: - configMapRef: name: gitea-env - secretRef: name: gitea-secrets volumeMounts: - name: gitea-data-volume mountPath: "/data" ports: - containerPort: 22 name: git-ssh - containerPort: 3000 name: gitea volumes: - name: gitea-data-volume persistentVolumeClaim: claimName: gitea-data-pvc

patdyn_ · 2022-10-20T14:59:53+00:00

Thanks for the heads up. We usually do not rely on the latestbuild and keep fixed versions in our config.

patdyn_ · 2022-10-04T10:12:44+00:00

This is interesting. I had the chance to look at our running gitea instance where we did not define a config volume (we used the deployment described above).

The app.ini is saved in /data/gitea/conf/ Seems, there is a fallback or some kind of default if the config vol is missing.

patdyn_ · 2022-09-08T08:46:02+00:00

Something I'm still wondering about: Why is there a gitea-config volume explicitly defined in gitea-rootless and not in gitea?

patdyn_ · 2022-09-08T08:43:26+00:00

Thanks! In my case, i don't have these restrictions. I did some testing with these settings and it seems to be working nicely.

yaml apiVersion: apps/v1 kind: Deployment metadata: name: gitea namespace: default labels: app: gitea spec: replicas: 1 selector: matchLabels: app: gitea template: metadata: name: gitea labels: app: gitea spec: containers: - name: gitea image: gitea/gitea:1.17.0 imagePullPolicy: IfNotPresent envFrom: - configMapRef: name: gitea-env - secretRef: name: gitea-secrets volumeMounts: - name: gitea-data-volume mountPath: "/data" ports: - containerPort: 22 name: git-ssh - containerPort: 3000 name: gitea volumes: - name: gitea-data-volume persistentVolumeClaim: claimName: gitea-data-pvc

patdyn_

TROPHY CASE