Mercurial > pub > dyncall > dyncall
view doc/README.NDS @ 166:d5705f226298
- added portasm support for adding .section .note.GNU-stack "hints" marking generated .o files from assembly files as not needing an executable stack
* needed to be done manually in assembly files, in contrast to C translation units where gcc adds such hints automatically
* this is for security, and better/easier integration of dyncall into other projects and builds, as dyncall doesn't need an executable stack
* thanks to Thorsten Behrens for bringing this up to our intention and providing a first analysis
* currently only done on Linux, but will be added across other platforms (where applicable) after some testing
author | cslag |
---|---|
date | Thu, 05 Jan 2017 11:07:29 +0100 |
parents | 3e629dc19168 |
children |
line wrap: on
line source
Build instructions for DynCall on Nintendo DS using devkitPro and NMake under Windows ============================================= To build the library, you have to configure it first. Since the NDS build uses devkitPro and NMake, assure to have them in your %PATH%. To configure the library, call one of the following, depending if you want to use the processor in ARM or THUMB mode: configure.bat /tool-gcc /target-nds-arm configure.bat /tool-gcc /target-nds-thumb Note that the /tool-gcc flag is needed, because we're using devkitARM (via devkitPro) which is based on the GCC toolchain. The /target-nds-* flags don't imply this. Then, call: nmake /F Nmakefile