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

compiled binary please #2

Open
shaderbytes opened this issue May 30, 2018 · 2 comments
Open

compiled binary please #2

shaderbytes opened this issue May 30, 2018 · 2 comments

Comments

@shaderbytes
Copy link

could you not provide the compiled binary?

I tried installing git , firstly no instructions on how to install the dependencies , even when searching it on my own it failed to install , the same for your instructions , my git installation using the bash tool did not recognize the commands cmake or make. I tried researching this and tried to add some files to some directory for getting make to work , i also installed cmake, still no luck all sorts of path errors when running cmake , also errors on the make command. this is now hours into just trying to get some textures from junkyard. I do own pinball arcade and did buy the table. I am a developer but not in this field of stuff , this is really annoying now because there is so little info on using or doing anything of this git stuff.. please just provide a compiled binary .. thanks

@JayFoxRox
Copy link
Owner

JayFoxRox commented May 30, 2018

I currently have no interest in doing this.

I assume you mean a binary for Windows?
The problem: I don't run / use Windows.

This means I can't easily compile or test this (other than cross-compiling and keeping my fingers crossed).
I think CI (kind-of best-effort releases) would be acceptable / preferrable, however, I won't be spending my time on this (lack of testing, and I dislike working on CI).

Also keep in mind that this is a CLI tool. So chances are that people who can't manage to compile it, are not able to use it properly either.
Some code also depends on guesswork, and might require changes before working. I haven't looked at recent PBA updates in over a year (again: I don't have Windows or any other platform to run PBA).

This is an open-source project and I've already spend a lot of time working on it. I believe it's other people responsibilty to add more features and enhance it.

I don't even use these tools myself at the moment.
I'm willing to review changes and make design suggestions, but I won't be adding new features currently.

Personally, I have projects which are more interesting and important to me, which also get more activity and donations. Therefore, it just feels more grateful to work on those things.

Your post is also the first development related activity / request that happened regarding this project in over a year. People did not even bother talking about #1 .
I don't think such low activity warrants investing more work for me personally.


As for the second issue regarding troublesome compilation:

I thought the tools were easily to compile for any C developer. They should work fine in MSYS / Windows, WSL, macOS, Linux and I know that at least 3 people compiled / used them with almost no problems.

CMake and make are standard tools, and libtxc_dxtn is a common lib as MESA uses it, so it's provided on most platforms (and the S3TC patent expired too). I'm actually surprised that vcpkg doesn't have it yet.

If you just want textures (which are still copyrighted by FarSight) you can probably use something like RenderDoc or apitrace. That would also work for other games too.

@shaderbytes
Copy link
Author

no worries then thanks for what is here already.

@JayFoxRox JayFoxRox mentioned this issue Oct 28, 2018
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

2 participants