busybox-w32/win32/env.c, branch realpath A mirror of https://github.com/rmyorston/busybox-w32.git https://git.lua4.win/busybox-w32/atom?h=realpath 2018-02-13T11:54:43+00:00 win32: always use safe API calls to manipulate environment 2018-02-13T11:54:43+00:00 Ron Yorston rmy@pobox.com 2018-02-13T11:54:43+00:00 urn:sha1:834805db9fe525dff26267fb7ba2794cee3ed51a It turns out that with the new toolchain safe API calls work on all all platforms. Even the original code from commit fa147bd7e works on Windows XP when built with the new tools. - Remove the unsafe environment manipulation via the environ array - Microsoft's putenv takes a copy of its argument so the string can be freed - Rewrite some routines and add more error checking win32: remove unused functions 2017-08-23T11:13:59+00:00 Ron Yorston rmy@pobox.com 2017-08-23T11:13:59+00:00 urn:sha1:d4dc5e4177056ae284c256278a853f51e347f13f The functions copy_environ and free_environ became unused following commit ac181bf54 "win32: simplify spawning applets". Allow different ways to manipulate environment for XP vs 64-bit 2015-07-03T13:12:47+00:00 Ron Yorston rmy@pobox.com 2015-07-03T13:12:47+00:00 urn:sha1:9fc98788e4fb1ea1f330d44c8b2019b3fe6444f7 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" 2014-12-18T10:08:26+00:00 Ron Yorston rmy@pobox.com 2014-12-18T10:08:26+00:00 urn:sha1:067f2e7eaf36deac1175eaf24eeb118adcd37179 This reverts commit fa147bd7ecb086f4fb9a4afea16b946693a822ce. Use putenv to implement unsetenv/clearenv 2014-11-23T17:35:35+00:00 Ron Yorston rmy@pobox.com 2014-11-23T17:35:35+00:00 urn:sha1:fa147bd7ecb086f4fb9a4afea16b946693a822ce 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 2012-04-23T09:14:18+00:00 Ron Yorston rmy@pobox.com 2012-04-23T09:14:18+00:00 urn:sha1:ece4cb7f6debdb741b8a43053aeea817b80f49e7 win32: implement clearenv() 2010-09-14T04:22:49+00:00 Nguyễn Thái Ngọc Duy pclouds@gmail.com 2010-09-14T04:12:56+00:00 urn:sha1:f24b8269a46035feef17eca1c2bf1176c5c23b90 win32: add getenv(), setenv(), unsetenv() and clearenv() 2010-09-10T08:50:00+00:00 Nguyễn Thái Ngọc Duy pclouds@gmail.com 2010-04-14T00:15:27+00:00 urn:sha1:43992d86844f4fa77b6e6613ce62b96d0e115bd5 clearenv() is not supported yet.