Thanks for writing this, it sounds like exactly what I need. I only know a little about embedded VC++, though, and I can't get it built.
I suggest reading the file path, parameters, and splash image file name from a file or the registry so you can distribute binaries. This would eliminate my current problem.
When I start eMbedded VC++, it says "This project does not contain any configurations whose platforms are supported by this installation of Microsoft eMbedded Visual C++. You will need to create a new supported configuration before you will be able to build, run, or debug your project."
I went to Build > Configurations... and added one for ARMV4. My target platform is XScale, but I'm not sure which CPU choice is right. When I clicked Close on the Configurations dialog, VC hung. I killed it and tried other combinations of CPU and Debug/Release, but it just hung every time.
I noticed there was a network adapter created when I installed VC, and it has a problem. Could that have something to do with it? If this is out of the scope of this forum, please suggest where I can search.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you using eMbedded VC++ 3.0? LnkLaunch code has only been tested with evc 3.0 -- the compiled binaries have been tested on PPC 2000, 2002, and 2003 Mobile.
Before you compile (rebuild all) select the ARM release option.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, that was it. I was using eVC 4.0. I downgraded to 3.0, and it worked.
One note: I had to change StdAfx.h from
#include <Afxwin.h>
to
#include "Afxwin.h"
I have another question. If I use LnkLaunch and wait for my program to fully load, LnkLaunch disappears. Then I use LnkLaunch again, but it starts a second instance of my program. I see you have code to prevent this from happening, but can you give me a hint about how to debug it?
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Never mind, I figured it out. My program changes its title a lot, so LnkLaunch wasn't finding it. I'm making some modifications to write the window handle to a file and use that to check for a running instance.
Apparently, I didn't need to change the Afxwin.h include as I mentioned before. Something else was causing the problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for writing this, it sounds like exactly what I need. I only know a little about embedded VC++, though, and I can't get it built.
I suggest reading the file path, parameters, and splash image file name from a file or the registry so you can distribute binaries. This would eliminate my current problem.
When I start eMbedded VC++, it says "This project does not contain any configurations whose platforms are supported by this installation of Microsoft eMbedded Visual C++. You will need to create a new supported configuration before you will be able to build, run, or debug your project."
I went to Build > Configurations... and added one for ARMV4. My target platform is XScale, but I'm not sure which CPU choice is right. When I clicked Close on the Configurations dialog, VC hung. I killed it and tried other combinations of CPU and Debug/Release, but it just hung every time.
I noticed there was a network adapter created when I installed VC, and it has a problem. Could that have something to do with it? If this is out of the scope of this forum, please suggest where I can search.
Are you using eMbedded VC++ 3.0? LnkLaunch code has only been tested with evc 3.0 -- the compiled binaries have been tested on PPC 2000, 2002, and 2003 Mobile.
Before you compile (rebuild all) select the ARM release option.
Thanks, that was it. I was using eVC 4.0. I downgraded to 3.0, and it worked.
One note: I had to change StdAfx.h from
#include <Afxwin.h>
to
#include "Afxwin.h"
I have another question. If I use LnkLaunch and wait for my program to fully load, LnkLaunch disappears. Then I use LnkLaunch again, but it starts a second instance of my program. I see you have code to prevent this from happening, but can you give me a hint about how to debug it?
Thanks.
Never mind, I figured it out. My program changes its title a lot, so LnkLaunch wasn't finding it. I'm making some modifications to write the window handle to a file and use that to check for a running instance.
Apparently, I didn't need to change the Afxwin.h include as I mentioned before. Something else was causing the problem.