Archived:Bldmake fails with "EPOCROOT environment variable must be capitalised" error (Known Issue)
hamishwillee
(Talk | contribs) m (Hamishwillee - Bot change of template (Template:KnowledgeBase) - now using Template:ArticleMetaData) |
hamishwillee
(Talk | contribs) m (Hamishwillee - Adding missing translation link) |
||
| Line 31: | Line 31: | ||
[[Category:Known Issue]][[Category:S60 2nd Edition]][[Category:S60 3rd Edition]][[Category:SDK]] | [[Category:Known Issue]][[Category:S60 2nd Edition]][[Category:S60 3rd Edition]][[Category:SDK]] | ||
| + | <!-- Translation --> [[ja:Bldmake が、"EPOCROOT environment variable must be capitalised"とエラーを表示]] | ||
Revision as of 07:33, 16 December 2011
Article Metadata
Compatibility
Platform(s): S60 2nd Edition
S60 3rd Edition
S60 3rd Edition
Article
Created: User:Technical writer 1
(30 Mar 2007)
Last edited: hamishwillee
(16 Dec 2011)
Overview
In some environments, the bldmake command may fail with the "EPOCROOT environment variable must be capitalised" error.
Description
This error is returned by the e32env.pm script when opening a pipe to the command line fails.
Solution
Typically this error is related to the PATH environment variable. bldmake fails if the system32 directory in the PATH is defined using the SystemRoot variable, that is
%SystemRoot%\system32
To fix this, modify the PATH to use an absolute path for \system32. For example,
C:\Windows\system32
Note: With current S60 SDKs (2nd Edition and later), EPOCROOT should not be explicitly defined. Instead, the active development configuration is selected with the devices.exe utility.
