Extract from http://tangentsoft.net/mysql++/ :

"... this problem has gone unfixed due to lack of interest for many
months, we no longer ship Borland project files with the package. We're
willing to reverse course on this if enough interest materializes... "

I hereby manifest my interest for Borland C++ support :-)...
(I use BDS 2006)

Cheers!

Frederic Laruelle.


--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw

Me too.

We're using BCB6

Richard

*********** REPLY SEPARATOR ***********

On 20.01.2006 at 15:02 Frederic Laruelle wrote:





--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw

Frederic Laruelle wrote:
The real problem is lack of an engaged maintainer. We need someone who
will 1) do the work to make the library build and run; 2) get the code
to the point that _all_ the examples run correctly; and 3) stick around
to provide continuing support. The last item is critical. Just making
the patch and then going away means that some time down the road, when
we break Borland support with some new feature, we'll again be
considering removing Borland support.

If we put Borland support back in the library, we want assurance that it
will not become a support nightmare in the future. If you can help
ensure that, read on.

The first issue is that with MySQL++ v2.1, we are looking at using
Bakefile to generate project files and such. Therefore, we need a
Borland user to check out the v2.1 branch from the Subversion repository
and try to get Bakefile to generate a project file that you can use to
successfully build MySQL++. This is almost guaranteed not to work
correctly right now, because even Unixy platforms aren't performing the
way I want yet. There's a lot of work to be done here.

Second, you need to test SSQLS. The last I heard, Borland compilers had
a 4K limit on macros, so the larger SSQLS macros couldn't be used. If
we are going to support Borland, we at least need to create a subset of
the SSQLS feature that will work for all supported compilers. If it
happens that the most recent version of the Borland compiler will build
MySQL++ without changes, then we have to ask whether we should just stop
supporting the older versions. All of these things require an active
maintainer. Even if someone bought me a copy of the Borland compiler, I
lack the time and interest to be the maintainer. We need an interested
Borland user to fill this role.

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw

Frederic Laruelle wrote:
First, obviously, you have to fix all the problems that you reported in
your other email. I didn't look at it carefully, but it all looks to be
fairly trivial stuff. The hardest part of making these changes is doing
so in such a way that you don't break other platforms, and that
maintains the current code style. Read the HACKERS file at the top of
the MySQL++ distribution, especially the "Adding Support for a Different
Compiler" section. But don't take it too literally because it is based
on the current build scheme. Instead of "makemake", think "Bakefile".

After that, you should port your changes to the v2.1 branch. This
should be trivial, as the Bakefile changes are the only thing on that
branch right now. You should be able to make a patch file with diff and
apply it directly.

Finally, you need to start playing with Bakefile to get it to create the
necessary project files automatically.

Since v2.0 settled down back in September, we've only made one release.
That was about two months ago. Releases tend to come in spurts,
though. I expect several soon after v2.1, just because of the way
people are.

So depending on your perspective, it's one release every few months, or
one release about every two weeks.

The first two items above you should probably be able to do in an hour
or two. The last one could be easy, or it could be a major time sink.
You won't know until you try.

If you don't yet understand Subversion or Bakefile, budget some time for
learning those tools.

I hope you can put more time in at the start than later on. Once the
port is working, you should only need to put in time to answer
Borland-specific questions on the mailing list, and to make patches to
fix up anything that breaks Borland support in the future. By far the
biggest part of the work is up front.

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw