Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't build, from the source code. #54

Open
migeru-san opened this issue Oct 28, 2021 · 4 comments
Open

Can't build, from the source code. #54

migeru-san opened this issue Oct 28, 2021 · 4 comments

Comments

@migeru-san
Copy link

I am trying to make a custom skin but can't compile from the source code 0.5.0.0.

Please help.

Screenshot 2021-10-28 114126

Screenshot 2021-10-28 114247

@Nielk1
Copy link
Owner

Nielk1 commented Oct 28, 2021

@migeru-san I can't tell what version you are on or what but if you're going to try to compile the program just to make a theme make sure that #1 you have the submodules also checked out (this should be automatic in most cases when you git pull) and #2 make sure you are on one of the tagged revisions and not on another revision which would be broken. The tags are applied on every release and those versions are the "stable" ones.

@migeru-san
Copy link
Author

migeru-san commented Oct 28, 2021

Microsoft Visual Studio Community 2019
Version 16.11.5 and I will try your advice and get back to you!

@Nielk1
Copy link
Owner

Nielk1 commented Oct 28, 2021

@migeru-san I mean of VSCView, that said I have some ideas.

If you don't mind making your working copy again, try cloning again with the --recursive argument to ensure the submodules are also cloned. If you don't want to clone again, in theory git submodule update --init should work in the terminal.

I use SourceTree which seems to default to adding the --recursive flag when cloning so I never noticed this issue.

@AL2009man
Copy link
Contributor

AL2009man commented Nov 12, 2021

I'm not sure if you're referring to Controller "custom skin".

If so, you could've grabbed any of the Controller's Theme files (either thru Release or indev builds), take the Controller theme's .json and start from there. That's how I did it while I was making default themes for DualSense, Steam Controller, Xbox and Nintendo Switch Pro Controller.

While the raw Controller Overlay files [for the Default Themes]haven't been released to the public (due to being SVGs), I wanna ensure Theme Makers to simply modify the Overlay image without touching the .json.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants