For security auditing purposes, keeping track of native source files

jirutka / luapak

Easily build a standalone executable for any Lua program

MIT License

200 stars 7 forks source link

For security auditing purposes, keeping track of native source files #4

Open eriksank opened 5 years ago

eriksank commented 5 years ago

For security auditing purposes, would it be possible to keep track of a copy of the *.h and *.c source files that went into building the native archives in .luapak/lib/lua/5.1?

They do not seem to remain available in the .luapak build folder.