Can executables be generated in a different directory?

In general, no.

The embedded systems created with BCLIDE and Code Development Systems employ comparatively few source files (contrast with desktop applications). We've always found it simpler to keep the project source files and generated executables in one Working Folder.


As of BCLIDE version 2.1 and later versions of Code Development System compilers, projects can include an Output Folder in which the compiler will generate executables. Check your product documentation to see if this is available in your CDS product.


Can multiple developers work with the same software through BCLIDE?

Yes, though the exact technique depends on your system and network setup.

  • BCLIDE projects (project file and source file) can reside on a shared drive. If the working folder is set to be on the shared drive as well, only one developer at a time can build (of course).

    BCLIDE keeps absolute paths for the source files; if everyone has the same drive mapping, this doesn't present a problem.

  • The better solution is for each developer to keep their own project file (.bcp file), but to use shared sources (whether shared drive or SCM'ed).

    BCLIDE project files are meant to be customized, with different tools and editor preferences (including code templates and auto-correct entries). Each project can point to the shared sources in a different way, allowing for hetrogenous computer networks.


How can I get BCLIDE to open an explorer window to the Working Folder?

Use Explorer as a tool.

  1. Choose Project|Properties.

    BCLIDE displays the Project Properties dialog.

  2. Select the Tools tab. In the Tools section, click Add Tool. BCLIDE will display fields for the new tool entry.

  3. In Tool Name, enter "Open Working Folder in Explorer".

    In Program, enter the path and executable name of the Windows Explorer. Use the Browse button to search for it, either in \Windows or \WINNT depending on your version of Windows.

  4. In Command Line, enter %w (substitution for the Working Folder). The special character button at right offers all the different substitutions available for this entry.

  5. Click Save Changes to create the new tool entry, and click OK to close the project properties.


I'm trying to replace a file with an updated version. Every recompile, the old version appears. What makes this happen?

Check to see if the BCLIDE is automatically saving an old version over top of the new version. If the file is open in BCLIDE when you put the new version in place, BCLIDE may overwrite it when you compile.

  1. Open Project|Properties.

  2. Choose the Editor tab of the Project Properties dialog.

  3. See if Save active source file or Save all source files is checked.

Simply close the edit window containing the source file, replace it with the new version, and open it again in BCLIDE.


The compiler is giving an "I/O Error" when I compile. What's wrong?

This may occur if the following points are true:

  • You are changing the name of the output files with the %s substitution in the Additional Options entry in the project properties (Compiler tab).

  • Your source file has a space in the file name.

The solution is to ensure that the file name to be created by the compiler is quoted in the Additonal Options entry in the project properties. For instance: