You can get rid of the environment variable using a win32 api call as explained
here:
http://stackoverflow.com/questions/2647429/c-windows-path-to-the-folder-where-the-executable-is-located
On Thursday, June 18, 2015 4:45 PM, Hotmail (ArbolOne)
arbol...@hotmail.ca wrote:
I found
Thank you. These patches solve with my current problem... However, I must
report that I find what I think are more AD related libraries in the 64-bit
build that are not in the 32-bit build. See below:
C:\gcc491w64attrib /s | grep -i ads.*.*a$
A
Hello,
I'm building a small utility that requires libraries libactiveds.a and
libadsnt.a. The libraries are included in the latest 64-bit toolchains, but not
on the 32-bit versions. I tested with
i686-4.9.1-release-win32-dwarf-rt_v3-rev3.7z (link fails because the libraries
are not included,
I would like to help to build a new installer. I suggest we use InnoSetup or
NSIS. I like InnoSetup because it's easier to mantain, but NSIS generates
smaller installer files. I can try to understand what the current installer
does, but it will go faster if you give me a summary.
On
