Homebrew DevkitARM - SDL_Image not found even when installed

  • Thread starter Thread starter Delipunch
  • Start date Start date
  • Views Views 1,223
  • Replies Replies 3

Delipunch

Member
Newcomer
Joined
Nov 7, 2015
Messages
16
Reaction score
7
Trophies
0
Age
27
XP
197
Country
United States
Trying my hand at porting something, I'm trying to compile something with devkitARM, but it complains that it can't find SDL_Image, but I've installed it manually and with the package manager (bu not at the same time, of course). Any ideas why it won't detect the lib, and how to fix the problem?

EDIT: console log
Code:
$ ./build.sh uqm config
Warning: host type 'arm-none-eabi' unknown. Using defaults.
'echo -n' capable echo found.
Sed stream editor found.
tr found.
Make found.
Cross-compiling to none.
GNU C compiler found.
We have a C preprocessor.
We have a C dependency generator.
We have a C compiler.
We have a linker.
Cross-compiling - assuming little-endian host.
Simple DirectMedia Layer version 1.2.15 found.
SDL_image not found.
 
Last edited by Delipunch,
Trying my hand at porting something, I'm trying to compile something with devkitARM, but it complains that it can't find SDL_Image, but I've installed it manually and with the package manager (bu not at the same time, of course). Any ideas why it won't detect the lib, and how to fix the problem?
the actual error message would be helpful at this point as the answer depends on whether the problem is with compiling or linking. If the issue is with compiling the you are either missing and include file or you need to add the portlibs directory to the include path. Linking issues are typically a result of a missing library reference in the makefile or the library order is incorrect.
 
the actual error message would be helpful at this point as the answer depends on whether the problem is with compiling or linking. If the issue is with compiling the you are either missing and include file or you need to add the portlibs directory to the include path. Linking issues are typically a result of a missing library reference in the makefile or the library order is incorrect.
Alright, I've put the console log up to the relevant point is the OP, the problem is with the build configuration script
 

Site & Scene News

Popular threads in this forum