Frequently Asked Questions
- Is it possible to run EDE from the command line only creating the makefile?
- The EDE Startup Halts at splash page screen on Windows NT4/2000/XP. How can I fix this?
- How can I solve thread synchronization issues on a computer that uses multiple CPUs.
- Can I have multiple instances of EDE running at the same time?
- How can I stop fatal errors from occurring while building a project?
- Is there documentation available for themake utility wmk.exe?
Question not listed? Contact Us.
Answers
Is it possible to run EDE from the command line only creating the makefile?
Yes, that is possible. Use the following command. It will force EDE to create the corresponding makefile and quit.
Or with even less output to the screen:
The EDE Startup Halts at splash page screen on Windows NT4/2000/XP. How can I fix this?
On a very few number of Windows NT4/2000/XP systems, EDE will halt its startup process while the splash screen is displayed. We have discovered that this problem is due to the fact that some sound devices do not support the Win32 API that we use.
Complete the following steps to remedy this problem:
- Using Windows Explorer, locate the file NOSOUND.REG in the <product>\bin directory. If the file isn't there, download it from the EDE web page.
- Using Windows Explorer, double-click on the NOSOUND.REG file to insert the proper registry entry to enable the fix.
Note:
If you would like to perform this step manually, you may do so with regedit.exe by inserting a DWORD value named "MenuControlSound" with a value of "0" into the following key :
EDE should now start up normally.
How can I solve thread synchronization issues on a computer that uses multiple CPUs.
EDE sometimes has thread synchronization issues when running on computers with multiple CPUs. This can manifest itself in various ways, including display problems.
If your system uses multiple processors, and you find that EDE is behaving in an unstable manner, try setting it up to use one CPU only. Two methods are available for running EDE using a single CPU. The first method is adding a command line parameter. The second method is adding a registry key. These methods are described next.
Adding a Command line Parameter
The "limit EDE CPU usage on multiprocessor machines" is:
-Processor = d
Where the d argument is the CPU to use.
EXAMPLES:
'-Processor=1' limits EDE to CPU 0
'-Processor=2' limits EDE to CPU 1
'-Processor=3' utilizes CPU 0 and CPU1
For a machine with multiple CPUs, we recommend that you change the desktop shortcut from:
<product>\bin\ede.exe
to
<product>\bin\ede.exe -Processor=1
(substitute the correct path for your installation of the product).
Adding a Register Key
A registry entry is available to select the CPU. The registry key is:
Add the DWORD value of the ProcessorMask. The value of ProcessorMask is selected from the table below.
| Value Name | DWord Value | For CPU..... |
|---|---|---|
| ProcessorMask | 1 | CPU 0 |
| ProcessorMask | 2 | CPU 1 |
| ProcessorMask | 4 | CPU 2 |
| ProcessorMask | 8 | CPU 3 |
Can I have multiple instances of EDE running at the same time?
Yes. EDE supports a number of command-line options, which are described in chapter 18 of the EDE User Guide (cwguide.pdf).
To get multiple instances of EDE, you have to modify the EDE shortcut(s) on your desktop and add the -M switch.
How can I stop fatal errors from occurring while building a project?
While building a project, one of the following fatal errors occur:
- "C:\Document.." cannot be found, wmk: *** action exited with value 1
- wmk: Macro too long:", wmk: *** action exited with value 1
The above errors are caused by the fact that EDE versions up to v3.1r2 do not support white space characters in environmental variables TMP, TEMP or TMPDIR. There are two workarounds to the problem. The first is to use a non-white space temporary folder reference. The other is to use 8-character notation to point to white space type folders. As an example suppose the temporary folder is referenced as below:
c:\program files\temp
Then the alternative would be:
c:\progra/TASKING/1\temp
If the above are unacceptable then as a final resort you can download EDE version v3.1r2.
Is there documentation available for the make utility wmk.exe?
Documentation of the make utility syntax can in general be found in the utilities section of the assembler manual of the product.
Use the following command to get the usage info for the Wmk make utility:
This should give the following output:
Summary of Options:
| -? | Show invocation syntax. |
| -D | Print makefile lines while being read. ``-DD'' produces more details. |
| -G | dirname Change to specified directory before reading a makefile. |
| -K | Don't remove temporary files. |
| -S | Undo the effect of ``-k''. |
| -W | target Treat target as if it has just been reconstructed. |
| -a | Always rebuild target without checking if it is out of date. |
| -c | Run as child process. |
| -d | Display all time comparisons which indicate a target is out of date. ``-dd'' produces more details. |
| -e | Environment variables override macro definitions. |
| -err | file Redirect all (error) output to specified file. |
| -f | file Use file instead of ``makefile''. ``makefile''. ``-'' denotes standard input. |
| -i | Ignore error codes returned by commands. |
| -k | On error, abandon the work for the current target only. |
| -m | file Name of invocation file, '-' means stdin. |
| -n | Perform a dry run. |
| -q | Question mode, don't build but set the exit status indicating whether or not the target is up to date. |
| -r | Do not read in the ``wmk.mk'' file. |
| -s | Silent mode. Do not print commands before execution. |
| -t | Touch the target files instead of reconstructing them. |
| -time | Display current date and time. |
| -w | Redirect warnings and errors to standard output. |
| -x | Show extended error message. |