Mercurial > pub > dyncall > dyncall
view doc/README.PSP @ 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
Cross-compile DynCall for PSP using PSP-SDK =========================================== Make sure the PSP SDK's is installed and that the build tools (e.g. psp-gcc) are in your PATH. Also make sure that your PSP SDK's include files are in your CPATH Status: ------- - dyncall: tests run ok. - dyncallback: all good. - dynload: unsupported due to missing dynamic linker and ELF headers. There are currently two ways to build dyncall for PSP. Build using configure and make: ------------------------------- $ ./configure --target=PSP $ make libdyncall libdyncallback Build using build script for gcc (using Makefile.generic): ---------------------------------------------------------- $ sh buildsys/scripts/batch-build-psp.sh