All-in-all, here is the configure I use on my Mac:
./configure -static -qt-gif -thread
P.S. Please, note that this still does not enable database (sql) support and since you are compiling statically if you
will need to work with a database, you will have to recompile.
After a very painful data-migration process
http://www.freshblurbs.com/rss.xml
The blog has moved to a new location: www.freshblurbs.com
Please, kindly update your RSS Reader with the new URL:http://www.freshblurbs.com/rss.xml
I apologize for the temporary inconvenience but in the long run the new server is going to be much more featue-rich and comfortable, benefiting both me and my kind readers.
08/30/05
Compiling QT3 on POSIX
When compiling a QT3 distribution on a unix system, there are several switches I would rather modify from their default values. For example, by default QT compiles in shared mode. Now, now - do you really want to send somebody an application you compiled and get cursed because that user does not have libraries your application requires? I am all for static compilation, hell with shared libraries! Then, I think GIF support is nice and thread support is a must. No idea why Trolltech guys have them disabled in the default.
posted by irakli, 18:29 | link | comments
08/29/05
Safari Update
Apple Inc. has released a Safari update today.
Safari is an extremely nice, fast and efficient browser on Mac OS X. The only big problem it had was with GMail. I guess it was due to the AJAX implementaion in Safari that made using gmail from Safari quite bulky. It seems like the latest update has fixed the issues, though. I have just installed the update and Gmail works pretty smoothly, so far.
Rock on, Apple!
posted by irakli, 16:35 | link | comments
08/28/05
Gmail Rocks - once more.
GMail is my most beloved email service. Not only because I get 1GB space for free but because it is extremely user-friendly. It is so nice that I do not even use POP access and always use it from the web.
Recently I have discovered one more very cool feature. I don't know how long this feature has been around, maybe for a very long time, but I must admit I only now discovered it and loved it. What I mean is hidden in the Settings under Accounts/Send E-Mail As and allows to send email as if it was sent from your another account... e.g. - your work email account?
This is quite important. Before, if I would forward some email to gmail, for the convenience of recieving it in one (and niceest) place, if then I wanted to reply to the message I had to go to the interface of the email address the message was recieved for. Otherwise, sender would be easily confused to recieve an answer to the email he sent to @umd.edu address, from address that is @gmail.com - not something to do.
Now that you got reasonably excited with me, I have to warn that gmail does not send emails in a totally transparent way. Clients at the receiving end have more than enough information to understand that email was sent from this-and-this@foo.com but on behalf of gmail.com. Some clients (I tested Outlook's web interface and Yahoo!) even warn about this.
I looked at the headers GMail generates and, indeed, it leaves a clear trail in the following header sections:
Return-Path: <whateveruser@gmail.com>
....
Sender: whateveruser@gmail.com
That's too sad. They really did not need to do such crap, because they validate the email account belongs to you, before activating it and I do not think there were any security issues. Yet, apparently, Google tries to play safe... too bad :(
But, whatever inconvenience, it is hard to deny that this service is still pretty handy and nice and since it is free, we should not be complaining too much, anyway :)
Recently I have discovered one more very cool feature. I don't know how long this feature has been around, maybe for a very long time, but I must admit I only now discovered it and loved it. What I mean is hidden in the Settings under Accounts/Send E-Mail As and allows to send email as if it was sent from your another account... e.g. - your work email account?
This is quite important. Before, if I would forward some email to gmail, for the convenience of recieving it in one (and niceest) place, if then I wanted to reply to the message I had to go to the interface of the email address the message was recieved for. Otherwise, sender would be easily confused to recieve an answer to the email he sent to @umd.edu address, from address that is @gmail.com - not something to do.
Now that you got reasonably excited with me, I have to warn that gmail does not send emails in a totally transparent way. Clients at the receiving end have more than enough information to understand that email was sent from this-and-this@foo.com but on behalf of gmail.com. Some clients (I tested Outlook's web interface and Yahoo!) even warn about this.
I looked at the headers GMail generates and, indeed, it leaves a clear trail in the following header sections:
Return-Path: <whateveruser@gmail.com>
....
Sender: whateveruser@gmail.com
That's too sad. They really did not need to do such crap, because they validate the email account belongs to you, before activating it and I do not think there were any security issues. Yet, apparently, Google tries to play safe... too bad :(
But, whatever inconvenience, it is hard to deny that this service is still pretty handy and nice and since it is free, we should not be complaining too much, anyway :)
