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

Error C2039 when compiling #468

Closed
ravennst opened this issue Nov 9, 2022 · 5 comments
Closed

Error C2039 when compiling #468

ravennst opened this issue Nov 9, 2022 · 5 comments
Labels
Needs more info Couldn't repro / more info needed

Comments

@ravennst
Copy link

ravennst commented Nov 9, 2022

I get a
'create': is not a member of 'image' (C2039) [Ln 16, Col 1] on image.h
when compiling in Visual Studio Code. I'm not a good coder and I'm just trying to use Godot with Voxel-Tools so I don't know if this is a big issue or not. I should note that Godot still runs despite this.

Screenshot_20221109-163205_Microsoft Remote Desktop.png

@Zylann
Copy link
Owner

Zylann commented Nov 10, 2022

Looks like you don't have the latest version or something? This file doesn't look like your screenshot https://github.com/Zylann/godot_voxel/blob/master/util/godot/image.h

@MGilleronFJ
Copy link

MGilleronFJ commented Nov 11, 2022

Note, there are two ways to build this:

  • As an engine module
  • As a GDExtension

Either way, you should be using the master branch of the repository. The gdextension branch is old now, and was used when it was still work-in-progress.
Note also, that building as a GDExtension is currently not guaranteed to produce a working library. There are a number of issues with GDExtension at the moment that are making this engine very likely to fail at runtime. As an alternative, you can build this engine as a module, or get one of the CI builds (see https://voxel-tools.readthedocs.io/en/latest/getting_the_module/)

@ravennst
Copy link
Author

Looks like you don't have the latest version or something? This file doesn't look like your screenshot https://github.com/Zylann/godot_voxel/blob/master/util/godot/image.h

I normally do a full fetch on both Godot and Voxel tools before I compile, Master branch on both, using GitHub Desktop. If what you guys are saying is true, I suspect that the files aren't getting updated locally when I bring up Visual Studio Code. I'll have to look into that.

@ravennst
Copy link
Author

Note, there are two ways to build this:

  • As an engine module
  • As a GDExtension

Either way, you should be using the master branch of the repository. The gdextension branch is old now, and was used when it was still work-in-progress.
Note also, that building as a GDExtension is currently not guaranteed to produce a working library. There are a number of issues with GDExtension at the moment that are making this engine very likely to fail at runtime. As an alternative, you can build this engine as a module, or get one of the CI builds (see https://voxel-tools.readthedocs.io/en/latest/getting_the_module/)

I've been using Master branch on both Godot and Voxel tools and compiling the entire engine. I'm thinking GitHub Desktop isn't updating the files locally properly so I will be looking into that.

@Zylann Zylann added the Needs more info Couldn't repro / more info needed label Nov 13, 2022
@ravennst
Copy link
Author

ravennst commented Nov 16, 2022

Ah HA! I found the problem. I accidentally nested the updated directory in the directory with the older version so fetching the latest build was putting it in the wrong place for the compiler. So instead of putting the files in modules/voxel, it was putting the updates into modules/voxel/voxel_tools. Updated & compiled without errors.

Thank you guys for pointing out that the files were out of date, it clued me in to what the problem was.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs more info Couldn't repro / more info needed
Projects
None yet
Development

No branches or pull requests

3 participants