Archived:Bldmake fails with "EPOCROOT environment variable must be capitalised" error (Known Issue)
hamishwillee
(Talk | contribs) |
hamishwillee
(Talk | contribs) m (moved Bldmake fails with "EPOCROOT environment variable must be capitalised" error (Known Issue) to Archived:Bldmake fails with "EPOCROOT environment variable must be capitalised" error (Known Issue)) |
||
| (2 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Category:Symbian C++]][[Category:Known Issue]][[Category:S60 2nd Edition (initial release)]][[Category:S60 3rd Edition (initial release)]][[Category:SDK]] | + | {{Archived|timestamp=20120314044011|user=roy.debjit| }} |
| + | [[Category:Symbian C++]][[Category:Known Issue]][[Category:S60 2nd Edition (initial release)]][[Category:S60 3rd Edition (initial release)]][[Category:SDK]][[Category:S60 3rd Edition FP1]][[Category:S60 3rd Edition FP2]] | ||
{{ArticleMetaData <!-- v1.2 --> | {{ArticleMetaData <!-- v1.2 --> | ||
|sourcecode= <!-- Link to example source code (e.g. [[Media:The Code Example ZIP.zip]]) --> | |sourcecode= <!-- Link to example source code (e.g. [[Media:The Code Example ZIP.zip]]) --> | ||
| Line 22: | Line 23: | ||
|author= [[User:Technical writer 1]] | |author= [[User:Technical writer 1]] | ||
<!-- The following are not in current metadata --> | <!-- The following are not in current metadata --> | ||
| − | |||
|id= KIS000609 | |id= KIS000609 | ||
}} | }} | ||
| − | + | == Description == | |
| − | + | {{Abstract|In some environments, the bldmake command may fail with the "EPOCROOT environment variable must be capitalised" error.}} This error is returned by the e32env.pm script when opening a pipe to the command line fails. | |
| − | In some environments, the bldmake command may fail with the "EPOCROOT environment variable must be capitalised" error. | + | |
| − | + | ||
| − | + | ||
| − | This error is returned by the e32env.pm script when opening a pipe to the command line fails. | + | |
==Solution== | ==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 | + | 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 S60 SDKs from S60 2nd Edition, EPOCROOT should not be explicitly defined. Instead, the active development configuration is selected with the devices.exe utility. | ||
<!-- Translation --> [[ja:Bldmake が、"EPOCROOT environment variable must be capitalised"とエラーを表示]] | <!-- Translation --> [[ja:Bldmake が、"EPOCROOT environment variable must be capitalised"とエラーを表示]] | ||
Latest revision as of 09:45, 15 June 2012
Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.
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
(15 Jun 2012)
Description
In some environments, the bldmake command may fail with the "EPOCROOT environment variable must be capitalised" error. 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 S60 SDKs from S60 2nd Edition, EPOCROOT should not be explicitly defined. Instead, the active development configuration is selected with the devices.exe utility.
