mysql-cocoa-users Mailing List for MySQL Objective C API for Cocoa (Page 3)
Brought to you by:
sergecohen
You can subscribe to this list here.
2002 |
Jan
(2) |
Feb
|
Mar
(14) |
Apr
(5) |
May
(23) |
Jun
(8) |
Jul
(13) |
Aug
(5) |
Sep
|
Oct
(1) |
Nov
(11) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(9) |
Feb
(6) |
Mar
(13) |
Apr
(2) |
May
(3) |
Jun
|
Jul
(5) |
Aug
(11) |
Sep
(18) |
Oct
(1) |
Nov
(15) |
Dec
(2) |
2004 |
Jan
(3) |
Feb
(3) |
Mar
(8) |
Apr
(1) |
May
(2) |
Jun
(3) |
Jul
(15) |
Aug
(36) |
Sep
(5) |
Oct
|
Nov
(6) |
Dec
(2) |
2005 |
Jan
(1) |
Feb
(11) |
Mar
(1) |
Apr
(6) |
May
|
Jun
(7) |
Jul
(3) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2006 |
Jan
(9) |
Feb
(5) |
Mar
(2) |
Apr
(1) |
May
(9) |
Jun
(2) |
Jul
(1) |
Aug
(4) |
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
2007 |
Jan
(23) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2008 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Lorenz T. <lo...@te...> - 2006-02-25 22:00:13
|
Hi, I have updated the old SMySQL framework in CocoaMySQL to the new =20 version 3.0.0 and it works good for MySQL 5 servers. When connecting =20 to a 4.1.14 server the application hangs and I get an error: *** -[NSConcreteData isEqualToString:]: selector not recognized [self =20= =3D 0x482b760] When connecting to a 4.0.18 server the application crashes and I get =20 an error: CocoaMySQL has exited due to signal 10 (SIGBUS). Both servers work fine with the old version of the framework. Has anybody had similar problems with the new framework or is this =20 problem because of some other code in CocoaMySQL? I have just checked =20= it with an old source of CocoaMySQL and it works fine until I change =20 the framework... Thanks, Lorenz --=20 lorenz textor ** sh ** eigerstrasse 21 8200 schaffhausen tf 052 - 624 27 91 ** zh ** schimmelstrasse 5 8003 z=FCrich tf 043 - 333 00 19 ** mobile 076 - 531 71 74 email lo...@te... |
From: Serge C. <ser...@us...> - 2006-02-01 23:32:44
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there; Just a short mail to mention that (with some help from Dave Winter), I've updated completly the web site, so if you want to go ahve a look and have any (constructive) comments ... please be my guest. Serge. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD4UUT5EPeG5y7WPsRAqMZAKD2uzLE8olS8TrSKBlQJzKmvR1NywCfUHhw +cNzZz4IuIS8hbhXhoxcuRg= =N62e -----END PGP SIGNATURE----- |
From: Serge C. <ser...@us...> - 2006-02-01 10:29:26
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Peter; The same way as before, the API has not changed on this part. Serge. Le 1 f=E9vr. 06 =E0 10:11, Peter Sampson a =E9crit : > Hi, > > Thank you, thank you Serge! This is very cool... > > Maybe I'm overlooking something, but how do you set the iConnection =20= > or MCPConnection parameters in this version? > > Thanks, > > Peter Sampson > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD4I115EPeG5y7WPsRApwNAKDiflk87C8G0vd46HL9IjFc2pHZ/gCfeYxP OL7BiOnIPpKivhRhdJW0oMo=3D =3DrI99 -----END PGP SIGNATURE----- |
From: Peter S. <pe...@ko...> - 2006-02-01 09:11:11
|
Hi, Thank you, thank you Serge! This is very cool... Maybe I'm overlooking something, but how do you set the iConnection or MCPConnection parameters in this version? Thanks, Peter Sampson |
From: Serge C. <ser...@us...> - 2006-01-31 16:50:11
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've just updated the file packages on sourceforge.... Can you try it know, and tell me if there is still a problem (well, =20 indeed I'd be also interested to hear if there is NO problem ;-). Thanks in advance. Serge. Le 31 janv. 06 =E0 17:22, Aaron Jacobs a =E9crit : > I've got a shiny new Intel iMac, so I'm going to give it a shot. =20 > If I figure it out, I'll share it with you. > > Aaron > > > On Jan 31, 2006, at 10:18 AM, Serge Cohen wrote: > >> Unfortunately for the Universal binary, I don't have a intel based =20= >> Mac, so I've now (fairly) easy way to get the libmysqlclient.a in =20 >> universal, hence (unless you can make this one yourself), you'll =20 >> have hard time with this one. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD35Uv5EPeG5y7WPsRAjSaAKCd8P4D07QXWUzvzO8jbPmy34dQ0ACfYmaI RVFLUHDl/jVhfxp3iXRtMeE=3D =3D0iDg -----END PGP SIGNATURE----- |
From: Aaron J. <aj...@ed...> - 2006-01-31 16:22:29
|
I've got a shiny new Intel iMac, so I'm going to give it a shot. If I figure it out, I'll share it with you. Aaron On Jan 31, 2006, at 10:18 AM, Serge Cohen wrote: > Unfortunately for the Universal binary, I don't have a intel based > Mac, so I've now (fairly) easy way to get the libmysqlclient.a in > universal, hence (unless you can make this one yourself), you'll > have hard time with this one. |
From: Serge C. <ser...@us...> - 2006-01-31 16:18:51
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Aaron; Have to check that and update them then... Thanks for pointing me to =20 that problem. Unfortunately for the Universal binary, I don't have a intel based =20 Mac, so I've now (fairly) easy way to get the libmysqlclient.a in =20 universal, hence (unless you can make this one yourself), you'll have =20= hard time with this one. Serge. Le 31 janv. 06 =E0 17:05, Aaron Jacobs a =E9crit : > Also, both of the source releases (.dmg and .tgz) on SourceForge =20 > are missing a ton of files. I need the source release so I can =20 > make universal binaries, and so I can comply with the license. :) > > Aaron -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD343e5EPeG5y7WPsRAvacAKDwPgBlZjuWZuCWHc7X0D1jdGCcwQCfbAhU I8MkcfgJErY+Wty8OyIVcbo=3D =3DD3Bm -----END PGP SIGNATURE----- |
From: Serge C. <ser...@us...> - 2006-01-31 16:17:40
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi; This is absolutely backward compatible, except for the name of the =20 header files and framework. The classes themselves have retained there names, so it should be a =20 very small amount of modification if you were using the previous =20 version. Serge. Le 31 janv. 06 =E0 16:57, Aaron Jacobs a =E9crit : > Serge, > > This sounds pretty cool, especially the out-of-box support for =20 > MySQL 4.1 authentication. I have a question, though, since you say =20= > there is little documentation. Is the framework backwards =20 > compatible, or is it required that we use the relational layer? > > Aaron Jacobs > > > On Jan 31, 2006, at 6:01 AM, Serge Cohen wrote: > >> It's been more than a year I was writing about it (not frequently =20 >> thought)... And I finally managed to roll it out yesterday. >> This is the version 3.0 of the framework. It's been renamed MCPKit =20= >> and contains a pseudo object/relational layer (which to answer a =20 >> recent question on the list is able to generate KVC/KVO classes). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD342X5EPeG5y7WPsRAme0AJ9s5E8B3wBWBN+AU+kaJxcdD779dACfeRQN CgmlR3sBy8Iez4yjeQDeVzw=3D =3DFGaV -----END PGP SIGNATURE----- |
From: Aaron J. <aj...@ed...> - 2006-01-31 16:05:56
|
Also, both of the source releases (.dmg and .tgz) on SourceForge are missing a ton of files. I need the source release so I can make universal binaries, and so I can comply with the license. :) Aaron |
From: Camille GOUREAU-S. <ca...@lu...> - 2006-01-31 16:05:21
|
Thanks a lot for the work. Congratulations. |
From: Aaron J. <aj...@ed...> - 2006-01-31 15:57:12
|
Serge, This sounds pretty cool, especially the out-of-box support for MySQL 4.1 authentication. I have a question, though, since you say there is little documentation. Is the framework backwards compatible, or is it required that we use the relational layer? Aaron Jacobs On Jan 31, 2006, at 6:01 AM, Serge Cohen wrote: > It's been more than a year I was writing about it (not frequently > thought)... And I finally managed to roll it out yesterday. > This is the version 3.0 of the framework. It's been renamed MCPKit > and contains a pseudo object/relational layer (which to answer a > recent question on the list is able to generate KVC/KVO classes). |
From: Serge C. <ser...@us...> - 2006-01-31 12:02:05
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello List; It's been more than a year I was writing about it (not frequently thought)... And I finally managed to roll it out yesterday. This is the version 3.0 of the framework. It's been renamed MCPKit and contains a pseudo object/relational layer (which to answer a recent question on the list is able to generate KVC/KVO classes). Most importantly it supports MySQL 4.1 authentication out of the DMG. There is also an application (MCPModeler) to deal with object/rel. models and generate the required class description. At some point I'd like to make it easy to use directly Xcode models for CoreData as a way to describe classes (and indeed that was one thing I was hoping to do before release, but I realised I'd never have time enough...). Documentation and website are lagging behind, again lack of time. If anyone want to provide some help on this front, you're very welcome !!! Nice coding and happy new year (it was about time ;-) Serge. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFD31Gg5EPeG5y7WPsRAqRRAJ4nDDBHzqPYAQx4N7ebQgwKuJhqywCg2Q4g bwbTsuSOnUldurOnpL/rs0s= =odkd -----END PGP SIGNATURE----- |
From: Peter S. <pe...@ko...> - 2006-01-05 01:19:30
|
Hello everyone, I'd like to capture data into my app with smysql, and then have the result conform to key-value coding so that we can work with objects in the bindings system, and with key-value coding. Has anyone had success with this? Can you give me a high-level overview of what needs to be done to get it working with KVC? Also, what changes need to be made to connect to mysql 4.1+, as I know the connection scheme has changed. Thanks so much. Cheers, Peter Sampson KOBRY, Inc. |
From: Lorenz T. <lo...@te...> - 2005-10-12 08:29:53
|
Hi, What is not compiling, the SMySQL framework or your project? What are the errors? I would use one of the binaries from the SMySQL project and include that in your project. Then you don't have to worry about compiling the framework. If you want to compile the framework, I think you need a proper installation of MySQL... For code samples about how to use the framework you can look at the source of CocoaMySQL which you find on http://cocoamysql. sourceforge.net. The basic steps for using the framework are: 1. add the framework to your project 2. if you are using the SMySQL_bundled, add a copy files build phase to add the framework to your application binary 3. import the SMySQL header where you want to use the framework Regards, Lorenz On Oct 12, 2005, at 05:20, mysql-cocoa-users- re...@li... wrote: > Hi everyone on this list... I'm not even sure if this list is still > alive. I'd very much like some help with working out stuff to do with > MySQL cocoa... does it still work? I can't seem to get it compliing > on My latest XCODE project. > > Can anyone help? > > Thanks in advance > Julian. |
From: Julian L. <ju...@co...> - 2005-10-12 01:44:36
|
Hi everyone on this list... I'm not even sure if this list is still alive. I'd very much like some help with working out stuff to do with MySQL cocoa... does it still work? I can't seem to get it compliing on My latest XCODE project. Can anyone help? Thanks in advance Julian. |
From: Serge C. <ser...@us...> - 2005-07-27 11:10:18
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Ferdinando; Indeed it is somehow a bug, the problem is that when the framework is =20= retrieving a decimal number from the database, it uses a =20 NSNumberWithFloat (basicaly a float or a double), for which the two =20 values are identical (within the precision range of the binary =20 representation). I have to check how 'decimal' columns are flagged by the =20 libmysqlcient... if there is a way to tell from the API it is a =20 decimal and not a REAL (or float...), then it is eeasy to modify the =20 framework so that it will use NSDecimalNumber instead of NSNumber for =20= these columns. I'll try to check in the next days and mail back to =20 give more precisions. Serge. Le 25 juil. 05 =E0 19:06, Ferdinando Pucci a =E9crit : > Hi, when i insert the value o.07 in a decimal field (lenght 5,2) =20 > cocoamysql inserts 0,07000000000000001. Is that a little bug? Thank =20= > you > > > > > > ___________________________________ Yahoo! Mail: gratis 1GB per i =20 > messaggi e allegati da 10MB http://mail.yahoo.it > > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dcli= ck > _______________________________________________ > Mysql-cocoa-users mailing list > Mys...@li... > https://lists.sourceforge.net/lists/listinfo/mysql-cocoa-users > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFC52uJ5EPeG5y7WPsRAnWFAKCK8nFXGmkMwIyVCKLS0VJ7GfaIlgCfcGW2 05mpCagzRu4AxhIfXVsgyDY=3D =3DkmA3 -----END PGP SIGNATURE----- |
From: Serge C. <ser...@us...> - 2005-07-27 11:07:13
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello James; I hope it's ok this goes also to the users-list : I have this =20 question from time to time ... The framework is based on the libmysqlclient library coming along =20 with mysql. This library is under GPL, hence the framework that I'm =20 developping has to be under GPL... unless I get a license from mysql =20 to be able to distribute it under non-GPL license. It's a bit of 'problematic' because I'm not the 'end-developper', and =20= I'm not interested in sub-licensing MyQSL to anyone willing to use my =20= framework under non-GPL license, hence in the past I've not done it =20 (the demand were never really urgents, nor pressing). I'd like to =20 find a solution where you get the MySQL license through MySQL and I =20 take care of giving you the license for the framework alone (provided =20= you have a MySQL license). I guess that you already have a license from MySQL to be able to use =20 there software without releasing your sources. In which case I would =20 think you're not really interested in buying yet another license of =20 MySQL... Serge. While I'm going into that, I'd like to know if some other users (on =20 this list at least) might be interested in getting a licensed version =20= of the framework? Le 25 juil. 05 =E0 16:36, James Burrows a =E9crit : > Hi Serge, > > I'm developing a Cocoa application based on MySQL and was thinking =20 > about using your framework. I'd like to be able to sell my =20 > application when it is done and was wondering if I would be able to =20= > do that if I used (linked against) your framework? My current =20 > understanding is that if I used your framework I would need to =20 > release the source of my own application (as it would be classed as =20= > a "work based on the program") and I could only charge for =20 > distribution/support? > > I would be really grateful if you could clarify this for me! > > Many thanks in advance, > > James. > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFC52rW5EPeG5y7WPsRAhf/AJ0a5Bzg6HtieajflEygOyzAUqN56wCfagSX XxPPQNi1FPVn7uaF8/PWoHA=3D =3Dc4nU -----END PGP SIGNATURE----- |
From: Ferdinando P. <puc...@st...> - 2005-07-25 17:04:29
|
Hi, when i insert the value o.07 in a decimal field (lenght 5,2) cocoamysql inserts 0,07000000000000001. Is that a little bug? Thank you ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it |
From: Aaron J. <aj...@ed...> - 2005-06-20 02:00:38
|
Well it's not going to be as easy as checking a box in Xcode, since libmysqlclient.a isn't built by an Xcode project. Apple has a description of how to do it with a Makefile-based project, but I don't know if that applies to libraries or only programs. I'll look into it when I have some time, but let us know if you figure it out. Aaron On Jun 19, 2005, at 8:57 PM, Jeff Kopmanis wrote: > If I'm not mistaken, I've always gotten the binary from the MySQL > folks (mysql.com). I'm guessing that a Universal Binary will need > to be compiled to get a Universal Binary libmysqlclient.a. > > Sound sane? > > I'll give it a whirl, but I'm notoriously bad at getting these > things to work. If anyone else has done this before, go for > it...no ego to bruise here. :) > > -Jeff. > > > On Jun 17, 2005, at 8:36 AM, Aaron Jacobs wrote: > > >> Of course, perhaps I should have tried this before I sent the e- >> mail. I guess I built the wrong target when I tested before. I'm >> getting an error, but I don't think it's the same as yours. My >> error is because the copy of libmysqlclient I have is built for >> ppc only, so it won't link it to an i386 binary. >> >> Does anyone know how I could build an i386 copy of libmysqlclient.a? >> >> Aaron >> >> >> On Jun 17, 2005, at 7:29 AM, Aaron Jacobs wrote: >> >> >> >>> I'm not using it as a framework or a library or anything. All I >>> have in my project is the source for the classes I need as well >>> as the libmysql_client library and the libmysql headers, since it >>> depends on those. The only warning I get is "Possible missing >>> call to [super dealloc]" for MCPNumber. I've been meaning to fix >>> that myself, but the MCPNumber class is designed really weirdly >>> and I don't know if there's a reason for that. >>> >>> Aaron >>> >>> >>> On Jun 16, 2005, at 11:38 PM, Jeff Kopmanis wrote: >>> >>> >>> >>> >>>> I haven't gotten the same errors twice, unfortunately. >>>> >>>> The current one is: >>>> /usr/bin/libtool: can't locate file for: -lmysqlclient.12.0.0 >>>> /usr/bin/libtool: file: -lmysqlclient.12.0.0 is not an object >>>> file (not allowed in a library) >>>> >>>> The last one complained about cclobj not being present for >>>> gcc-3.3, which was puzzling, since gcc-4.0 is supposed to be the >>>> current compiler (I checked that with gcc_select). >>>> >>>> Did you have to set any paths or other particulars? Also, there >>>> are alot of warnings regarding stuff like bad return types, bad >>>> typing and such, but nothing that claimed it was going to break >>>> stuff. >>>> >>>> Oh...I'd assumed that if there are precompiled headers that I'd >>>> need to recompile those as well...is that true? >>>> >>>> I'll admit my programming skills are a bit rusty, but this >>>> really seems to be less obvious than it could be. Serves me >>>> right for staying in system admin for so long... >>>> >>>> Thanks, >>>> >>>> -Jeff. :) >>>> >> >> > > Jeff Kopmanis > kop...@gm... > http://www.kopmanis.com > > > |
From: Jeff K. <kop...@gm...> - 2005-06-20 01:57:28
|
If I'm not mistaken, I've always gotten the binary from the MySQL folks (mysql.com). I'm guessing that a Universal Binary will need to be compiled to get a Universal Binary libmysqlclient.a. Sound sane? I'll give it a whirl, but I'm notoriously bad at getting these things to work. If anyone else has done this before, go for it...no ego to bruise here. :) -Jeff. On Jun 17, 2005, at 8:36 AM, Aaron Jacobs wrote: > Of course, perhaps I should have tried this before I sent the e- > mail. I guess I built the wrong target when I tested before. I'm > getting an error, but I don't think it's the same as yours. My > error is because the copy of libmysqlclient I have is built for ppc > only, so it won't link it to an i386 binary. > > Does anyone know how I could build an i386 copy of libmysqlclient.a? > > Aaron > > > On Jun 17, 2005, at 7:29 AM, Aaron Jacobs wrote: > > >> I'm not using it as a framework or a library or anything. All I >> have in my project is the source for the classes I need as well as >> the libmysql_client library and the libmysql headers, since it >> depends on those. The only warning I get is "Possible missing >> call to [super dealloc]" for MCPNumber. I've been meaning to fix >> that myself, but the MCPNumber class is designed really weirdly >> and I don't know if there's a reason for that. >> >> Aaron >> >> >> On Jun 16, 2005, at 11:38 PM, Jeff Kopmanis wrote: >> >> >> >>> I haven't gotten the same errors twice, unfortunately. >>> >>> The current one is: >>> /usr/bin/libtool: can't locate file for: -lmysqlclient.12.0.0 >>> /usr/bin/libtool: file: -lmysqlclient.12.0.0 is not an object >>> file (not allowed in a library) >>> >>> The last one complained about cclobj not being present for >>> gcc-3.3, which was puzzling, since gcc-4.0 is supposed to be the >>> current compiler (I checked that with gcc_select). >>> >>> Did you have to set any paths or other particulars? Also, there >>> are alot of warnings regarding stuff like bad return types, bad >>> typing and such, but nothing that claimed it was going to break >>> stuff. >>> >>> Oh...I'd assumed that if there are precompiled headers that I'd >>> need to recompile those as well...is that true? >>> >>> I'll admit my programming skills are a bit rusty, but this really >>> seems to be less obvious than it could be. Serves me right for >>> staying in system admin for so long... >>> >>> Thanks, >>> >>> -Jeff. :) > Jeff Kopmanis kop...@gm... http://www.kopmanis.com |
From: Aaron J. <aj...@ed...> - 2005-06-17 12:36:41
|
Of course, perhaps I should have tried this before I sent the e- mail. I guess I built the wrong target when I tested before. I'm getting an error, but I don't think it's the same as yours. My error is because the copy of libmysqlclient I have is built for ppc only, so it won't link it to an i386 binary. Does anyone know how I could build an i386 copy of libmysqlclient.a? Aaron On Jun 17, 2005, at 7:29 AM, Aaron Jacobs wrote: > I'm not using it as a framework or a library or anything. All I > have in my project is the source for the classes I need as well as > the libmysql_client library and the libmysql headers, since it > depends on those. The only warning I get is "Possible missing call > to [super dealloc]" for MCPNumber. I've been meaning to fix that > myself, but the MCPNumber class is designed really weirdly and I > don't know if there's a reason for that. > > Aaron > > > On Jun 16, 2005, at 11:38 PM, Jeff Kopmanis wrote: > > >> I haven't gotten the same errors twice, unfortunately. >> >> The current one is: >> /usr/bin/libtool: can't locate file for: -lmysqlclient.12.0.0 >> /usr/bin/libtool: file: -lmysqlclient.12.0.0 is not an object file >> (not allowed in a library) >> >> The last one complained about cclobj not being present for >> gcc-3.3, which was puzzling, since gcc-4.0 is supposed to be the >> current compiler (I checked that with gcc_select). >> >> Did you have to set any paths or other particulars? Also, there >> are alot of warnings regarding stuff like bad return types, bad >> typing and such, but nothing that claimed it was going to break >> stuff. >> >> Oh...I'd assumed that if there are precompiled headers that I'd >> need to recompile those as well...is that true? >> >> I'll admit my programming skills are a bit rusty, but this really >> seems to be less obvious than it could be. Serves me right for >> staying in system admin for so long... >> >> Thanks, >> >> -Jeff. :) |
From: Aaron J. <aj...@ed...> - 2005-06-17 12:29:46
|
I'm not using it as a framework or a library or anything. All I have in my project is the source for the classes I need as well as the libmysql_client library and the libmysql headers, since it depends on those. The only warning I get is "Possible missing call to [super dealloc]" for MCPNumber. I've been meaning to fix that myself, but the MCPNumber class is designed really weirdly and I don't know if there's a reason for that. Aaron On Jun 16, 2005, at 11:38 PM, Jeff Kopmanis wrote: > I haven't gotten the same errors twice, unfortunately. > > The current one is: > /usr/bin/libtool: can't locate file for: -lmysqlclient.12.0.0 > /usr/bin/libtool: file: -lmysqlclient.12.0.0 is not an object file > (not allowed in a library) > > The last one complained about cclobj not being present for gcc-3.3, > which was puzzling, since gcc-4.0 is supposed to be the current > compiler (I checked that with gcc_select). > > Did you have to set any paths or other particulars? Also, there > are alot of warnings regarding stuff like bad return types, bad > typing and such, but nothing that claimed it was going to break stuff. > > Oh...I'd assumed that if there are precompiled headers that I'd > need to recompile those as well...is that true? > > I'll admit my programming skills are a bit rusty, but this really > seems to be less obvious than it could be. Serves me right for > staying in system admin for so long... > > Thanks, > > -Jeff. :) > > On Jun 17, 2005, at 12:20 AM, Aaron Jacobs wrote: > > >> Jeff, >> >> What were the errors? I use the SMySQL source files in my project >> for work, and have produced a universal binary for that project >> without any errors. I don't have an Intel machine to test it on >> and thus don't know if it runs, but there were no compiler errors. >> >> Aaron Jacobs >> >> >> On Jun 16, 2005, at 8:26 PM, Jeff Kopmanis wrote: >> >> >> >>> At WWDC, I was trying to get my favorite Cocoa app, CocoaMySQL, >>> to compile as a Universal Binary. The CocoaMySQL code worked >>> fine, but naturally, my binary SMySQL framework hadn't been >>> ported for the i386 yet. I've tried a number of times, but Xcode >>> 2.1 seems to have some problems dealing with the framework code >>> and its new habitat under Xcode 2.1. >>> >>> Have there been attempts to produce a Universal Binary version of >>> the SMySQL framework yet, and if so, what changes were necessary >>> to get the thing to compile? >>> >>> I was tempted to copy the errors and such into this message, but >>> I'm really not sure they would have been much help, since there >>> are so many settings and configurations that go into Xcode >>> compiling. Lemme know if there's something specific that would >>> help. >>> >>> Thanks, >>> >>> -Jeff. :) >>> >>> Jeff Kopmanis >>> kop...@gm... >>> http://www.kopmanis.com >>> >> >> > > Jeff Kopmanis > kop...@gm... > http://www.kopmanis.com > > > |
From: Jeff K. <kop...@gm...> - 2005-06-17 04:38:48
|
I haven't gotten the same errors twice, unfortunately. The current one is: /usr/bin/libtool: can't locate file for: -lmysqlclient.12.0.0 /usr/bin/libtool: file: -lmysqlclient.12.0.0 is not an object file (not allowed in a library) The last one complained about cclobj not being present for gcc-3.3, which was puzzling, since gcc-4.0 is supposed to be the current compiler (I checked that with gcc_select). Did you have to set any paths or other particulars? Also, there are alot of warnings regarding stuff like bad return types, bad typing and such, but nothing that claimed it was going to break stuff. Oh...I'd assumed that if there are precompiled headers that I'd need to recompile those as well...is that true? I'll admit my programming skills are a bit rusty, but this really seems to be less obvious than it could be. Serves me right for staying in system admin for so long... Thanks, -Jeff. :) On Jun 17, 2005, at 12:20 AM, Aaron Jacobs wrote: > Jeff, > > What were the errors? I use the SMySQL source files in my project > for work, and have produced a universal binary for that project > without any errors. I don't have an Intel machine to test it on > and thus don't know if it runs, but there were no compiler errors. > > Aaron Jacobs > > > On Jun 16, 2005, at 8:26 PM, Jeff Kopmanis wrote: > > >> At WWDC, I was trying to get my favorite Cocoa app, CocoaMySQL, to >> compile as a Universal Binary. The CocoaMySQL code worked fine, >> but naturally, my binary SMySQL framework hadn't been ported for >> the i386 yet. I've tried a number of times, but Xcode 2.1 seems >> to have some problems dealing with the framework code and its new >> habitat under Xcode 2.1. >> >> Have there been attempts to produce a Universal Binary version of >> the SMySQL framework yet, and if so, what changes were necessary >> to get the thing to compile? >> >> I was tempted to copy the errors and such into this message, but >> I'm really not sure they would have been much help, since there >> are so many settings and configurations that go into Xcode >> compiling. Lemme know if there's something specific that would help. >> >> Thanks, >> >> -Jeff. :) >> >> Jeff Kopmanis >> kop...@gm... >> http://www.kopmanis.com > Jeff Kopmanis kop...@gm... http://www.kopmanis.com |
From: Aaron J. <aj...@ed...> - 2005-06-17 04:21:17
|
Jeff, What were the errors? I use the SMySQL source files in my project for work, and have produced a universal binary for that project without any errors. I don't have an Intel machine to test it on and thus don't know if it runs, but there were no compiler errors. Aaron Jacobs On Jun 16, 2005, at 8:26 PM, Jeff Kopmanis wrote: > At WWDC, I was trying to get my favorite Cocoa app, CocoaMySQL, to > compile as a Universal Binary. The CocoaMySQL code worked fine, > but naturally, my binary SMySQL framework hadn't been ported for > the i386 yet. I've tried a number of times, but Xcode 2.1 seems to > have some problems dealing with the framework code and its new > habitat under Xcode 2.1. > > Have there been attempts to produce a Universal Binary version of > the SMySQL framework yet, and if so, what changes were necessary to > get the thing to compile? > > I was tempted to copy the errors and such into this message, but > I'm really not sure they would have been much help, since there are > so many settings and configurations that go into Xcode compiling. > Lemme know if there's something specific that would help. > > Thanks, > > -Jeff. :) > > Jeff Kopmanis > kop...@gm... > http://www.kopmanis.com |
From: Jeff K. <kop...@gm...> - 2005-06-17 01:26:59
|
At WWDC, I was trying to get my favorite Cocoa app, CocoaMySQL, to compile as a Universal Binary. The CocoaMySQL code worked fine, but naturally, my binary SMySQL framework hadn't been ported for the i386 yet. I've tried a number of times, but Xcode 2.1 seems to have some problems dealing with the framework code and its new habitat under Xcode 2.1. Have there been attempts to produce a Universal Binary version of the SMySQL framework yet, and if so, what changes were necessary to get the thing to compile? I was tempted to copy the errors and such into this message, but I'm really not sure they would have been much help, since there are so many settings and configurations that go into Xcode compiling. Lemme know if there's something specific that would help. Thanks, -Jeff. :) Jeff Kopmanis kop...@gm... http://www.kopmanis.com |