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

update to autotrace 0.40.0 #1

Closed
jnweiger opened this issue Sep 1, 2018 · 5 comments
Closed

update to autotrace 0.40.0 #1

jnweiger opened this issue Sep 1, 2018 · 5 comments

Comments

@jnweiger
Copy link

jnweiger commented Sep 1, 2018

Hey Scott, if you want to refresh your windows binary here, please check out the latest version of the source at https://github.com/jnweiger/autotrace , thanks!

@scottvr
Copy link
Owner

scottvr commented Dec 31, 2018

Thanks for the notice! It seems with the latest versions, there is no need for me to maintain binary releases anymore. Good work!

@jnweiger
Copy link
Author

jnweiger commented Jan 1, 2019

Yes, you can simply refer to the windows release of 0.40 at https://github.com/autotrace/autotrace/releases -- it has a crude nsis installer thing for windows. You could do me a favour and test it. I rarely use windows...

@scottvr
Copy link
Owner

scottvr commented Jan 6, 2019

I tested the packages and the installer. The resultant executables do work on my 64-bit Windows 7 machine. A few comments: Maybe change the default install location to not use the "Program Files (x86)" directory as it does now. Since your binaries are 64-bit, "\Program Files\" is where they go. Since you include libs in the install path too- another (32-bit) application looking for the DLL for libiconv, for example, will choke when it finds your x86-64 DLL in its "SYSWOW64" executable path. In other words, autotrace.exe will work from this directory, but you run a risk of breaking some other app by putting 64-bit shared libs in the 32-bit Program Files path, which is probably not-desired.

I am going to go ahead and build your 0.40 since my target was statically linked (and with libpng, which I notice you didn't build support for) and replace what's in my repo with new binaries. Presumably a fair number of people have used/are using this repo due to its mention in a few different docs/threads, so I don't want to render the legacy docs out there non-working.

@jnweiger
Copy link
Author

jnweiger commented Jan 8, 2019

If I did it right, the two issues should be fixed. There are new builds at https://github.com/autotrace/autotrace/releases/tag/travis-20190108.39

@scottvr
Copy link
Owner

scottvr commented Jan 13, 2019

Hey cool! Thanks. I have updated the README here to point to your repo.

@scottvr scottvr closed this as completed Jan 13, 2019
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