Re: removing all dependency on MSVCR*.DLL
- From: Cartoper <cartoper@xxxxxxxxx>
- Date: Fri, 20 Jun 2008 07:57:13 -0700 (PDT)
On Jun 20, 9:55 am, David Wilkinson <no-re...@xxxxxxxxxxxx> wrote:
I guess I don't understand the problem. MSVCRT*.dll is just the standard C
runtime library. Its equivalent will be on any C/C++ platform.
Well, right now my install needs to check to see if the VS2005 Runtime
is installed and if it isn't, the installer installs it. The last
thing I want to happen is someone try to run my install and the
install craps out because this library needs the VS2005 runtime and it
isn't present. This is the sole reason that code is still VC6.
There is also the annoying warnings in VS2005/2008 about how one is
not suppose to be using the old strcpy (and the like) functions in
favor of strcpy_s version. I know that strcpy isn’t safe by nature so
I code around that to make sure it is safe and I don’t want to have to
deal with all these different “options” in the source code when
compiling for Windows, Linux, and OSX.
Or if you use static linking (/MT) everywhere you will not have any DLL
dependency on Microsoft platform.
Have you thought carefully about the necessity of porting this app to Mac/Linux?
Most Windows programs run pretty well under CrossOver Mac/Linux. Even if your
app does not run on CrossOver out of the box, it would almost certainly be less
trouble to make it run, rather than port the whole application.
David,
I have thought LONG and HARD about how important is having the
application cross platform. I am developing software for
photographers. How many Mac or Linux versions will I sell? I am
guessing not a ton, but it is as much about marketing as anything
else. It is very common for folks to ask me if my solution runs on
Mac, had a gentleman the other day ask, “Does your solution run on
Mac? I use Windows myself, but a good friend of mind use Mac.” Will
he not buy mine if it is Windows only? Don’t know, but I do know
being able to answer positively to the question will give him a warm
fuzzy feeling about my solution compared to the others.
I don’t understand it, but for some reason photographers like to see
Mac support. I think they are like me, always wanting to switch, but
never being able to justify the cost. But when it comes to buying
software, they like knowing that the Windows solution they purchase is
also available on Mac if they do decide to switch.
As far as Linux: the solution is client/server. I have had current
users ask if the client could run on Linux. They are trying to reduce
the cost per client with the free OS. I am going to purchase a 3rd
framework that supports all three platforms, so Linux server should be
basically free, with respect to development time, so I figured why
not. If the ROI of testing the server is too low, I will drop it and
only offer the client on the Linux platform.
Cartoper
.
- Follow-Ups:
- Re: removing all dependency on MSVCR*.DLL
- From: David Wilkinson
- Re: removing all dependency on MSVCR*.DLL
- References:
- removing all dependency on MSVCR*.DLL
- From: Cartoper
- Re: removing all dependency on MSVCR*.DLL
- From: David Wilkinson
- removing all dependency on MSVCR*.DLL
- Prev by Date: itoa
- Next by Date: Re: itoa
- Previous by thread: Re: removing all dependency on MSVCR*.DLL
- Next by thread: Re: removing all dependency on MSVCR*.DLL
- Index(es):
Relevant Pages
|
