Building a standalone : unexpected stack files in build
Posted: Tue Jun 10, 2014 9:37 am
I hope that this is a simple user error on my part: I have an application that uses a splash stack and several library stacks. I build for both Mac and Windows and I expect the windows build to comprise two files and a folder e.g. MyApp.exe , revsecurity.dll and the folder Externals which contains the database drivers. This has been the typical collection of files and folders for the past three months.
Now when I make a build I am getting all the other stacks that are part of my application appearing as files in the build. I have not knowingly made any changes that should cause this new unwanted behaviour and would like to get back to the situation where the stack files are not visible. The Mac OS build has a similar set of readable stack files all contained in the "package" folder whereas earlier builds did not reveal the code.
Any ideas on how I can get back to the situation where library and other stacks are hidden from the endusers file system?
Any ideas how this can just "happen" - the "ghost in the machine" perhaps ?
many thanks
Simon
Now when I make a build I am getting all the other stacks that are part of my application appearing as files in the build. I have not knowingly made any changes that should cause this new unwanted behaviour and would like to get back to the situation where the stack files are not visible. The Mac OS build has a similar set of readable stack files all contained in the "package" folder whereas earlier builds did not reveal the code.
Any ideas on how I can get back to the situation where library and other stacks are hidden from the endusers file system?
Any ideas how this can just "happen" - the "ghost in the machine" perhaps ?
many thanks
Simon