[go: up one dir, main page]

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

Acid.dll missing. #102

Open
Darkzeroprojects-coding opened this issue Oct 4, 2020 · 5 comments
Open

Acid.dll missing. #102

Darkzeroprojects-coding opened this issue Oct 4, 2020 · 5 comments

Comments

@Darkzeroprojects-coding
Copy link

I build the engine but the editor n stuff won't run because some reason the Acid.Dll never built.
Already built and compiled other dependencies,and sofar got them close to fine,and place the directitories.
Cmake generates the projects fine,I build,and outside errors and warnings built alot.
But Acid.dll is still not been showing up.

@Hay1tsme
Copy link

Having the same issue. The Acid project isn't being build due to a wall of "unresolved externals." Unsure what the issue could be, as everything seems to build properly. I've attached my log as it's too long to reasonably post. Hopefully this helps get the issue resolved.
acid.log

@mattparks
Copy link
Member

I was not able to replicate on my develop branch using the latest releases of Visual Studio 2019 or 2017, with vcpkg enabled or disabled. Perhaps RelWithDebInfo and all of these linking errors relating to bullet3 are a hint. I'll retry my testing from master using Release later. You might have more success building the develop branch of this repo, I updated bullet3 a few months back along with other tweaks to the build system.

@Hay1tsme
Copy link

I attempted to build the develop branch but am still seeing similar errors building the Acid project. Seems like something's up with Bullet, and I'm not sure but I may have messed up building freetype.
acid-develop.log

@Hay1tsme
Copy link

I tried using the packages downloaded using vcpkg instead of building them myself, and while there are fewer messages, it still will not build. I'm also new to vcpkg and couldn't figure out how to get any of the debug libraries through it, but I'm not sure if that has anything to do with it.
acid-develop.log

@Hay1tsme
Copy link

I solved the problem by doing everything through Visual Studio, instead of using CMake GUI to generate the project, then opening it with Visual Studio to build.

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