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

Project paths for beaengine are absolute #11

Closed
ghost opened this issue May 8, 2016 · 3 comments
Closed

Project paths for beaengine are absolute #11

ghost opened this issue May 8, 2016 · 3 comments

Comments

@ghost
Copy link

ghost commented May 8, 2016

The projectpaths for beaengine are absolute
(C:\Users\Owner...)

They should be relative to the project
(..\beaengine...)

@Timboy67678
Copy link
Collaborator

both libraries are precompiled and included in the git, i will change these for people who need to recompile them but its a non-issue atm

@ajkhoury
Copy link
Owner

How is this a bug? Most projects don't even include the library dependencies and expect the dev to know what they're doing. It's not a bug, or an issue,

@Timboy67678
Copy link
Collaborator

i thought i had removed the bug label, my bad

@Timboy67678 Timboy67678 removed the bug label May 15, 2016
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