OSAL | TI OSAL on Visual Studio | Code Editor library

The CopyFile API expects file names for both source and destination files. Your code passes a directory name for the destination. This causes the API to fail. You need to append the file name for the destination as well.

Besides that, there are several other issues with your code:

• The path separator on Windows is a backslash (\). Your are mixing forward slashes (/) and backslashes. Depending on the arguments passed, the system won't translate forward slashes to backslashes, before passing them on to lower-level file I/O API's.
• You are calling GetLastError too late. You need to call it immediately, whenever it is documented to return a meaningful value. Do not intersperse it with any other code, however trivial it may appear to you. That code can modify and invalidate the calling thread's last error code.
• Your code assumes ASCII-encoded strings. This will stop working, when dealing with files containing non-ASCII characters. This is quite common.
• new wchar_t[...] buys you nothing over std::vector, except the possibility to introduce bugs.
• Your MultiByteToWideChar-based string conversion implementation makes (undue) assumptions about the code unit requirements of different character encodings. Those assumptions may not be true. Have the API calculate and tell you the destination buffer size, by passing 0 for cchWideChar.
• Your string conversion routine ignores all return values, making bugs ever so likely, and unnecessarily hard to diagnose.

Pointers in C++ are a little bit different than their C counterpart. It should be invoked using the keyword new for efficient memory management. double *pbsal = new double[2];

Now pbsal[0] and pbsal[1] are just double values. And the loop should be i<2not i<=2.

The "main" rule app (thats builds all that needs to be build) must have as dependency the needed files (the object files). This way make will first build them by calling the appropriate rule.

Thus, you rule needs to be:

The documentation is written for the OXF, not for the SMXF Framework. As far as I know there is no real documentation for adapting an SMXF but.. the SMXF is there as a model (Check your /LangC/smxf directory) this should make it easier to create an adapter. Do you really need the SMXF or would an OXF suffice (or even another Framework like RXF?

Walter