|IRC Nick||Time (GMT-7)||Message|
|FireBreathBot||04:05||JIRA issue http://jira.firebreath.org/browse/FIREBREATH-88 issue commented by xlink "Thanks, the last version from github is successifully builded!"|
|FireBreathBot||08:05||JIRA issue http://jira.firebreath.org/browse/FIREBREATH-88 issue closed by richard "я рад, что смог помочь =)"|
|jshanab_wcw||08:05||Good morning. I am playing with Mac build. I am new to mac, I installed xcode, but do not know how to start it or even find it
oh, found it, nevermind
did you install xcode4?
|taxilian||09:05||jshanab_wcw: let me know how things go =] have you finally updated to 1.5?|
|jshanab_wcw||09:05||no, I have not. :-( two many irons in the fire (especially with amazon recruiter teasing me)|
|taxilian||09:05||I'll give you a tip: if you port to mac using 1.4, you will wish you'd upgraded first
don't do it
upgrade to 1.5 before porting
|jshanab_wcw||09:05||ok, Is that about the drawing choices? I may be avoiding that as I was considering using sdl|
you can't avoid drawing choices
you can only see if SDL can work with the choices you hav e
|taxilian||09:05||the simplest is if you can use CoreGraphics; you get a CGContextRef from the browser and you draw when instructed
and again, you want to use 1.5 because that's been refactored and is much simpler
if you want you could skype me and I can give you the rundown
|jshanab_wcw||09:05||Thanks for the offer, I got minutes to get this building again. I spent the 3-day refactoring our code.|
|jshanab_wcw||09:05||I am running macos in VirtualBox so I play when the other machine compiles :-)|
|taxilian||09:05||hehe. you should try the 1.6 branch with PCH support… *significant* increase in build speed on windows|
|_pq_||09:05||lol "command depressed"|
|jshanab_wcw||09:05||I want to make our project like your build system. I really like your CMAKE stuff, a work of art|
|taxilian||09:05||why thank you. it still has a few rough edges, though|
|taxilian||09:05||one of these days I'll fix 'em
|FireBreathBot||09:05||Found 1 matching file(s) in the master branch. First 1 are:
|_pq_||09:05||log messages for keyboard events
want to congratulate with the developer which wrote them
|taxilian||09:05||hehe. I'm not actually sure. might have been neilg_
looks like it
|neilg_||09:05||That sounds like it was me|
|taxilian||09:05||neilg_: next time, use the FireBreath log messages instead of NSLog|
|neilg_||09:05||I actually thought it was all commented out!
|linearray||09:05||speaking of logging, one of the reasons for cmake in the FAQ is "If you decide you want to start using logging, you need to regenerate your project.". What kind of logging is this about?
htmlLog has some serious performance implications, btw
talking about log4cplus
which still hasn't been documented by anyone :-P
well, log4cplus is the default FireBreath logging tool; you can provide your own
|linearray||09:05||so, how DO i turn it on? :)|
|taxilian||09:05||tell you what, do a search for log4cplus on logs.firebreath.org
then I'll answer any other questions you have
|jshanab_wcw||09:05||taxilian. I watched the videos again last night for the MAC. (boy those will be fun to update, like for event stuff) Anyway, is there a place on line that has the steps, i want to do the symlink trick|
which symlink trick?
I am just going thru the exampl at the moment
|taxilian||09:05||just make a symlink to the plugin in ~/Library/Internet Plugins|
|jshanab_wcw||09:05||Love the paths in Mac. Where is the plugin built to, I seem to remeber it looked like a directory?
or is it just in the debug folder?
|taxilian||09:05||yeah, it's projects/<project name>/Debug
I should fix that
it's easy to fix
mainly I havne't because now everyone is used to it :-P
|jshanab_wcw||09:05||why do you say fix? beause it does not have the np in forn t of it?|
|taxilian||09:05||no, because it doesn't build to the same place that it does on windows
it should be consistent
|jshanab_wcw||09:05||oh. Is a plugin on mac and archive or packae of sorts, I do not see npBasicMediaPlugin.so|
|taxilian||09:05||it's a .plugin directory
|jshanab_wcw||09:05||OK, interesting. Do I need to "ln -s <dir> npBasicMediaPlayer"|
|taxilian||09:05||no, you ln -s to the .plugin dir|
|jshanab_wcw||09:05||righ, but what do i call the link :-)|
|taxilian||09:05||whatever you want, as long as it ends in .plugin
if it were me, I'd just to ln -s <path/to/plugin.plugin> and keep the name the same
darn, doesnt't load the plugin and I did fully shutdown FF. Now weather or not it built is another matter, xcode is "diferent"
|taxilian||10:05||shouldn't need to shut down FF
make sure the plugin is built, though
did the plugin directory exist?
what is the path that you symlinked to?
|jshanab_wcw||10:05||darn, can't cut-n-paste. "ln -s ~/archiver/src/common/FireBreath/Examples/Build/Projects/BasicMedaiPlayer/Debug/BasicMediaPlayer.plugin BasicMediaPlayer.plugin"|
|taxilian||10:05||does it show up in about:plugins?|
It seems to contain a plist, but not much else. lemme check the xcode.
|taxilian||10:05||there should be a binary in Contents/MacOS|
|jshanab_wcw||10:05||Alright, I am not getting xcode. I right click build the ALL target? is that close|
|taxilian||10:05||what version of xcode?|
|taxilian||10:05||I don't think there is a right click to build
but if there is that would work
I usually just hit command+b
|jshanab_wcw||10:05||How obscure. Now I get build errors, but you have to go look for them. No default output window. I am gonna have to play with this later. VS won't debug again|
|taxilian||10:05||cmd+shift+b gives you a build window
that tells you where the errors are
these things can be found in the menus as well
I just don't remember exactly where
probably in "build" or "run"
|jshanab_wcw||10:05||ok looks like it is missing g++ "Command /Developer/usr/bin/g++-4.2 failed with exit code 1" :-)|
there is a "…" button to the right of that message
maybe above it a bit
that'll show you the command line and actual output
could be useful
|jshanab_wcw||10:05||There is no build or run!|
|taxilian||10:05||hang on, let me pull up xcode
ok, there is a build and a run
did you forget that on a mac the menu is at the top of the screen?
not in the window itself?
|jshanab_wcw||10:05||OH, so embarrased, no boost. Guess what I forgot...|
|taxilian||10:05||lol. are you using system boost?|
|jshanab_wcw||10:05||I forgot the git of the subproject. it is a new machine (Virtually)|
|taxilian||10:05||it should have fixed that when you ran prepmac.sh
you did run prepmac.sh, right? ;-)
hmm. unless you're using a really old version
I'm really serious, though… take the time to upgrade to 1.5. it's really not that hard
|jshanab_wcw||10:05||I guess I am using system boost.
I will, after work or on the weekend.
|taxilian||10:05||… so your work isn't interested enough in having things work well that you can take a couple of hours to update on company time?|
|jshanab_wcw||11:05||Uh, er, um. I didn't mean it that way. Just don't want to add any more varaibles on the working windows release while working on the mac port.|
|taxilian||11:05||you are absolutely right… deal with one thing at a time
deal with 1.5 upgrade first
then deal with mac
it's up to you, of course… I'm just telling you it's a bad idea
otherwise you're going to end up solving a bunch of problems either differently than you'll need to in 1.5 or that you wouldn't have needed to in 1.5
|jshanab_wcw||11:05||Got it. Right now I am learning mac and how to develop pn it. nothing critical just get my feet wet with the examples.|
|taxilian||12:05||anyone here know openssl well at all?|
|kylehuff||12:05||not exactly "well" -- but I *might* be able to help|
|taxilian||12:05||so I need to basically clear out the cert store
if I just do X509_STORE_new and then SSL_CTX_set_cert_store will it work?
or will I be suddenly engulfed in a burning inferno of death?
or somewhere in between?
|kylehuff||12:05||that should work, IIRC, the only time I did that, I passed the new cert store with add_cert(cert_store, cert)
(and I think, the cert was a null X509
|taxilian||12:05||right; that's what I'm doing
all CA certs have to be converted to PEM to work, right?
|kylehuff||12:05||yeah, I believe so|
|taxilian||12:05||I imported several CAs and they didn't work; probably didn't convert them to PEM
is there any way to tell what format they are in just by looking at them?
|kylehuff||13:05||pk12 and DER files are binary I think, and PEM should be base64|
|taxilian||13:05||hmm. I must already have DER, then|
|kylehuff||13:05||I finished an openssl related project quite a few months ago -- this is reminding me of how glad I was to be done messing with it...|
|taxilian||13:05||yeah… it's… fun....|
|neilg_||13:05||Isn't it? I feel your pain...
But you're right about CA certs need to be in .pem format
I had to do that for our plugin
|taxilian||13:05||so I tried using openssl to get the CA cert and it isn't working :-/|