×
Namespaces

Variants
Actions
(Difference between revisions)

Archived:Bldmake fails with "EPOCROOT environment variable must be capitalised" error (Known Issue)

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Adding missing translation link)
debjit.roy (Talk | contribs)
(Debjit.roy -)
Line 1: Line 1:
[[Category:Symbian C++]]
+
[[Category:Symbian C++]][[Category:Known Issue]][[Category:S60 2nd Edition]][[Category:S60 3rd Edition]][[Category:SDK]]
 
__NOTOC__
 
__NOTOC__
 
__NOEDITSECTION__
 
__NOEDITSECTION__
Line 21: Line 21:
 
}}
 
}}
  
 +
{{Archived|timestamp=20120314044011|user=roy.debjit| }}
 
==Overview==
 
==Overview==
 
In some environments, the bldmake command may fail with the "EPOCROOT environment variable must be capitalised" error.
 
In some environments, the bldmake command may fail with the "EPOCROOT environment variable must be capitalised" error.
Line 30: Line 31:
 
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<br>%SystemRoot%\system32<br>To fix this, modify the PATH to use an absolute path for \system32. For example,<br>C:\Windows\system32<br>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.
 
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<br>%SystemRoot%\system32<br>To fix this, modify the PATH to use an absolute path for \system32. For example,<br>C:\Windows\system32<br>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.
  
   [[Category:Known Issue]][[Category:S60 2nd Edition]][[Category:S60 3rd Edition]][[Category:SDK]]
+
    
 
<!-- Translation --> [[ja:Bldmake が、"EPOCROOT environment variable must be capitalised"とエラーを表示]]
 
<!-- Translation --> [[ja:Bldmake が、"EPOCROOT environment variable must be capitalised"とエラーを表示]]

Revision as of 07:40, 14 March 2012

Template:KBKI

Article Metadata
CompatibilityArticle
Created: User:Technical writer 1 (30 Mar 2007)
Last edited: debjit.roy (14 Mar 2012)

Archived.pngArchived: 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}}.

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.

139 page views in the last 30 days.
×