[fpc-pascal] Looking for fpc developer
Hi, In my spare time I'm developing a framework for developing business applications: data-model, application server, business objects. It should be released as open source under lgpl. However, I encounter problems, especially with respect to the linux x86_64 platform. Therefore I'm looking for a experienced fpc developer who will prepare the project for alpha release with running demo's for the linux x86_64 platform. You won't get rich with it, but you will be adequately paid on a monthly basis. Also, I'm interested contacting anyone working on a similar project, i.e. o.s. business applications. Perhaps efforts can be coordinated. Constantijn ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] The Interface to MySQL has changed on version
> You cannot. Mysql is a pain to maintain. They break interface compatibility almost every release. So its mean that mysql is difficult to followed? if yes, is there any other way to access mysql like odbc maybe? - Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out.___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] The Interface to MySQL has changed on version
On Mon, 8 Oct 2007, Andi Purwito wrote: > > > You cannot. Mysql is a pain to maintain. They break interface compatibility > almost every release. > So its mean that mysql is difficult to followed? Yes. The best is to stick to 1 version of MySQL as long as possible. > if yes, is there any other way to access mysql like odbc maybe? You can do that, but it's not cross-platform, and slow... Michael. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] The Interface to MySQL has changed on version
Op maandag 08-10-2007 om 22:16 uur [tijdzone -0700], schreef Andi Purwito: > > You cannot. Mysql is a pain to maintain. They break interface compatibility > almost every release. > So its mean that mysql is difficult to followed? Yes. (It's not for nothing that ppl still use mysql 4.0 and 4.1) Also, it's only the client. So you can use a mysql4.1-client-lib with a mysql 5.0 server. > if yes, is there any other way to access mysql like odbc maybe? You could offcourse use some db-library, like sqldb or ZEOS. Then the Zeos/sqldb-developers have to follow mysql for you... Joost. ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Compiling FPC 2.2 on Mac OS X / i386
Hello, I would like to compile FPC. Do I need a special make tool? When I type make all, I get many error messages, apparently because the make tool from Apple is not the right one. Thanks for any tips! Cheers, Tobias http://www.superflexible.com ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
Re: [fpc-pascal] Compiling FPC 2.2 on Mac OS X / i386
On 09 Oct 2007, at 15:08, Tobias Giesen wrote:
I would like to compile FPC. Do I need a special make tool? When I
type make all, I get many error messages, apparently because the
make tool from Apple is not the right one.
No, it's because the makefile probably does not find your installed
FPC, as its installation location (/usr/local/bin) is not in the path
by default. Try
export PATH=/usr/local/bin/:"$PATH'
make all
or, if you use (t)csh:
setenv PATH /usr/local/bin:{$PATH}
make all
Jonas
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
[fpc-pascal] Re:The Interface to MySQL has changed on version by version Andi Purwito
> mysqlku.pas(16,18) Error: Identifier not found "TMYSQL" > mysqlku.pas(16,18) Error: Error in type definition > mysqlku.pas(18,22) Error: Identifier not found "TMYSQL_ROW" > mysqlku.pas(18,22) Error: Error in type definition > mysqlku.pas(74,17) Error: Operator is not overloaded > mysqlku.pas(76,32) Error: Illegal qualifier > mysqlku.pas(76,35) Error: Illegal expression > mysqlku.pas(77,35) Error: Illegal qualifier > mysqlku.pas(77,38) Error: Illegal expression > mysqlku.pas(78,37) Error: Illegal qualifier > mysqlku.pas(78,44) Error: Illegal expression > > It's look that the interface has changed. But where can we get and follow its > change? Instead of using 'TMYSQL_ROW' try 'MYSQL_ROW' (omit the T). That way, you can compile the code with both versions of Mysql since the old units have the type definitions without the 'T' also. To Michael or whoever knows: Did the C header files use 'T' back then but not now? ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
