×
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
Forum Nokia KB (Talk | contribs)
extkbeditor2 (Talk | contribs)
m
Line 2: Line 2:
 
__NOEDITSECTION__
 
__NOEDITSECTION__
 
{{KBKI}}
 
{{KBKI}}
{|border="2" cellspacing="0" cellpadding="4" width="100%"
+
{{KnowledgeBase
|colspan = "2"|
+
|id=KIS000609
=====bldmake fails with "EPOCROOT environment variable must be capitalised" error=====
+
|platform=S60 2nd Edition<br>S60 3rd Edition
|
+
|devices=
=====KIS000609=====
+
|category=Symbian C<nowiki>++</nowiki>
 +
|subcategory=SDK & Tools
 +
|creationdate=March 30, 2007
 +
|keywords=
 +
}}
  
|-
+
==Overview==
|
+
In some environments, the bldmake command may fail with the "EPOCROOT environment variable must be capitalised" error.
=====Overview=====
+
|colspan = "2"|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.
=====Category=====
+
|colspan = "2"|Symbian C<nowiki>++</nowiki>
+
  
|-
+
==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<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.
=====Subcategory=====
+
|colspan = "2"|SDK & Tools
+
  
|-
 
|
 
=====Reported against=====
 
|colspan = "2"|S60 2nd Edition<br>S60 3rd Edition<br>
 
 
|-
 
|
 
=====Date identified=====
 
|colspan = "2"|March 30, 2007
 
 
|-
 
|
 
=====Symptoms=====
 
|colspan = "2"|-
 
 
|-
 
|
 
=====Detailed description=====
 
|colspan = "2"|This error is returned by the e32env.pm script when opening a pipe to the command line fails.
 
 
|-
 
|
 
=====How to reproduce=====
 
|colspan = "2"|-
 
 
|-
 
|
 
=====Solution=====
 
|colspan = "2"|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:Symbian C++]][[Category:S60 2nd Edition]] [[Category:S60 3rd Edition]] [[Category:IDE/SDK]]
 
[[Category:Known Issue]][[Category:Symbian C++]][[Category:S60 2nd Edition]] [[Category:S60 3rd Edition]] [[Category:IDE/SDK]]

Revision as of 18:04, 24 October 2008


Template:KBKI

Article Metadata
CompatibilityArticle
Created: (30 Mar 2007)
Last edited: extkbeditor2 (24 Oct 2008)

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.

132 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×