busybox-w32 - A mirror of https://github.com/rmyorston/busybox-w32.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Allow different ways to manipulate environment for XP vs 64-bit	Ron Yorston	2015-07-03	1	-0/+59
\| \| \| \| \| \| \| \| \| \| \|	Commit fa147bd 'Use putenv to implement unsetenv/clearenv' allowed BusyBox to run on ReactOS but broke it on Windows XP so it was reverted. It turns out that the same change is required on 64-bit Windows. Reinstate the 'safe' environment manipulation code but make it a configuration option. Add a config file for 64-bit Windows that does the right thing.
*	Revert "Use putenv to implement unsetenv/clearenv"	Ron Yorston	2014-12-18	1	-46/+11
\| \| \| \|	This reverts commit fa147bd7ecb086f4fb9a4afea16b946693a822ce.
*	Use putenv to implement unsetenv/clearenv	Ron Yorston	2014-11-23	1	-11/+46
\| \| \| \| \| \| \| \| \| \|	noexec applets failed on ReactOS 0.3.17. This was because the environment was being manipulated directly using the environ pointer. Implementing unsetenv and clearenv using putenv fixes the problem. WIN32 putenv doesn't allow environment variables to have empty values. This was the case before and it's still the case after this change. Shell variables are fine.
*	win32: add popen implementation that uses shell	Ron Yorston	2012-04-23	1	-1/+3
\|
*	win32: implement clearenv()	Nguyễn Thái Ngọc Duy	2010-09-14	1	-1/+10
\|
*	win32: add getenv(), setenv(), unsetenv() and clearenv()	Nguyễn Thái Ngọc Duy	2010-09-10	1	-0/+119
	clearenv() is not supported yet.