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

source of compiler issues #54

Closed
Cavencruiser opened this issue Jul 6, 2024 · 5 comments
Closed

source of compiler issues #54

Cavencruiser opened this issue Jul 6, 2024 · 5 comments

Comments

@Cavencruiser
Copy link

https://github.com/doomhack/GBADoom/blame/3bd2cf34fb66dd60f9b66efe25cc1d6945a21f74/source/hu_lib.c#L80

@Cavencruiser Cavencruiser changed the title causing compiler issues source of compiler issues Jul 6, 2024
@Emendo12
Copy link

I have this compiler issue as well.

@FrenkelS
Copy link

What happens when you remove that line?

@doomhack
Copy link
Owner

Seems that the Doom code play fast and loose with pointer types. Assigning pointers (*) to double pointer (**) vars etc.

The code is wrong but worked before because a pointer is a pointer.....

I'll try to fix this over the next couple of evenings...

@doomhack
Copy link
Owner

@doomhack
Copy link
Owner

Adding the -fpermissive flag 'fixes' this. The code is wrong but it's been wrong since 1993...

If you do a fresh pull, it should build with latest DevKitPro.

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

4 participants