hConvert – New Developer’s Tool

hConvertJaeden Amero has developed a program that will allow for “kiddies” (newer developers) to convert .c, .cpp, and .h files into .bin files. It seems that Jaeden got his inspiration for this program after hearing too much of complaining from the senior developers in the NDS scene about the “kiddies” not binary files. The program’s structure and function is best described by the developer himself – “It’ll parse through a (currently limited) hex based, comma delimited, “{” starting, “};”, terminated dump of binary data and spit out a little .bin file. Super useful!.” With that being said, here’s an important note by the developer –

“Using bin files, devkitARM, and the default makefile for devkitARM (which uses bin2o) is the recommended way of linking binary data into your program. However, the most portable way of including binary data in your program is through an isolated translation unit, ie a .c file a textual representation of the data to be linked. Many kiddies would make the mistake of then including this file, “#include “my_gfx_thingy.c”, which is bad bad bad. NEVER DO IT. The proper way to make it a truly isolated and portable translation unit is to make a .h file that will refer to it using the extern keyword. That would look like this in the .h file (not the .c) which we include from where ever we want to reference the graphic, continuing our previous example, “extern const uint16 my_gfx_thingy[];”.”

Note: This program currently supports x86 Linux and Mac OS X. There is no native windows support at the momment.

Download: [hConvert]

Via Jaeden Amero

hConvertJaeden Amero has developed a program that will allow for “kiddies” (newer developers) to convert .c, .cpp, and .h files into .bin files. It seems that Jaeden got his inspiration for this program after hearing too much of complaining from the senior developers in the NDS scene about the “kiddies” not binary files. The program’s structure and function is best described by the developer himself – “It’ll parse through a (currently limited) hex based, comma delimited, “{” starting, “};”, terminated dump of binary data and spit out a little .bin file. Super useful!.” With that being said, here’s an important note by the developer –

“Using bin files, devkitARM, and the default makefile for devkitARM (which uses bin2o) is the recommended way of linking binary data into your program. However, the most portable way of including binary data in your program is through an isolated translation unit, ie a .c file a textual representation of the data to be linked. Many kiddies would make the mistake of then including this file, “#include “my_gfx_thingy.c”, which is bad bad bad. NEVER DO IT. The proper way to make it a truly isolated and portable translation unit is to make a .h file that will refer to it using the extern keyword. That would look like this in the .h file (not the .c) which we include from where ever we want to reference the graphic, continuing our previous example, “extern const uint16 my_gfx_thingy[];”.”

Note: This program currently supports x86 Linux and Mac OS X. There is no native windows support at the momment.

Download: [hConvert]

Via Jaeden Amero

Add a Comment

Your email address will not be published. Required fields are marked *