From 45f51649c4958710290abd50630ff9ba252e8196 Mon Sep 17 00:00:00 2001 From: Riccardo Spagni Date: Sun, 8 May 2016 23:04:35 +0200 Subject: [PATCH] add those double-spaces --- ...he-kovri-dev-meeting-held-on-2016-05-08.md | 208 +++++++++--------- 1 file changed, 104 insertions(+), 104 deletions(-) diff --git a/_posts/2016-05-08-logs-for-the-kovri-dev-meeting-held-on-2016-05-08.md b/_posts/2016-05-08-logs-for-the-kovri-dev-meeting-held-on-2016-05-08.md index 032bc7ce..4a758fd9 100644 --- a/_posts/2016-05-08-logs-for-the-kovri-dev-meeting-held-on-2016-05-08.md +++ b/_posts/2016-05-08-logs-for-the-kovri-dev-meeting-held-on-2016-05-08.md @@ -10,108 +10,108 @@ author: dEBRUYNE / fluffypony # Logs -**\** Hi fluffypony -**\** hiiii -**\** was just about to check if you're around :) -**\** Hi everyone, I think meeting-bot is still online -**\** yes it is -**\** coming through loud and clear on this side -**\* anonimal** reading backlog -**\** Hi moneromoo. -**\** Hi psi, uncrustify configs? Can you explain? -**\** uncrustify is a code styler for c/c++ -**\** I've never heard of it, plz tell me more psi? -**\** it auto formats the code -**\* psi** gets relevant links -**\** https://github.com/uncrustify/uncrustify -**\** I know that psi, but why for *.conf? -**\** i don;t understand? -**\** what about *.conf? -**\** oh anonimal -**\** not for *.conf -**\** he means conf file for uncrustify matching our coding style -**\** damn lag -**\* psi** waits to catch up -**\** fluffypony: right -**\* anonimal** back -**\** wb -**\** To answer the question, no I don't have an uncrustify config for kovri. -**\** Just a simple .vimrc. -**\** I can take a look at creating a config after #174 is resolved. -**\** fluffypony: I saw your comment in #56, what system are you runnning? -**\** anonimal: Ubuntu 14.04 -**\** and there's no Boost 1.59 / 1.60 available -**\** but that little hack worked -**\** 1.54 should work though -**\* anonimal** triple checks -**\** I can't use 1.54 -**\** incompatible with Monero -**\** monero needs .56 or higher ? -**\** .55 or higher -**\** kk -**\** so basically .59 or higher if you want both -**\** I need about 5-15 minutes to build on bsd and osx so I can open the new linkage error tickets I talked about in #174 -**\** kk -**\** :\ -**\* anonimal** the only time I have is now and a bit later but the meeting is now so I want to throw it into the topic -**\* anonimal** still compiling, should be done in 5 or so -**\** #monero-dev, FYI, our meetings have always been more organized, on-point, and I've almost always been prepared. -**\** This one caught me off guard. -**\** (last minute suggestion by fluffypony) -**\** Sorry for the wait. -**\** don't stress, ours are always by the seat of our pants -**\* anonimal** opening tickets -**\** Hmf, I need to work with the bsd a bit more before posting. -**\** Anyway, https://github.com/monero-project/kovri/issues/175 -**\** I'm only sitting with this again since I left off < 24 hours or so ago so, -**\** I haven't drawn any conclusions yet. -**\** Has anyone seen this before? #monero-dev? -**\* fluffypony** clicks -**\** moneromooo: seen anything like that before ? -**\** "Undefined symbols for architecture x86_64" -**\** The usual 'Undefined symbols for architecture x86_64' has been an osx complaint on this machine in the past. -**\** Not as such. I've seen plenty of really annoying linking issues though. -**\** this is gcc on OS X tho, right ? -**\** fluffypony: Yes. -**\** maybe we're chasing our tails on that -**\** I don't have time to deal with clang. If we want multi-distro builds, I need to streamline our process. -**\** for macosx, clang won't build because it doesn't like the things I did for the reseed rewrite and, -**\** I don't have time to keep-up with llvm development. -**\** So, thoughts? -**\** rewrite everything in C :-P -**\** lol -**\** ok my suggestion is that we eschew OS X / BSD compatibility for the moment -**\** until we can fix Clang support -**\** Thanks moneromoo. I'm glad this isn't just a kovri thing. -**\** rather than trying to fudge it -**\** Well that's the problem, this won't be the only issue. -**\** yeah I know -**\** And I'll end up wasting time juggling compilers instead of working on other things. -**\** I mean that can be a later piece of work -**\** let's focus on getting it working on one Linux and Windows, where we're running gcc and it's fine -**\** fluffypony: what part will be the later piece of work? -**\** anonimal: fixing Clang incompatibilities -**\** I don't use OSX btw, so kinda ignore what I said above. -**\** Ok sounds great, I'll focus on linux/win building. -**\** Should we remove osx/bsd build instructions from BUILDING.md? -**\** Or I'll just open the bsd ticket and maybe someone will see it? -**\** yeah, I think let's make a note that it's broken on OS X / BSD for the moment, and that contributors are welcome to fix -**\** kk -**\** Ok, I'll add the note. -**\** Any other questions/comments on #175? -**\** no not yet -**\** I mean no not atm, lol -**\** Ok, I'll add a note in #174 about what we discussed. -**\** And part 1) in #174, apparently there is an env variable I can set to get it to work. -**\** Not the first travis issue I've had to deal with. -**\** Oh well, they are growing quite nicely IMHO. -**\** travis issues are growing quite nicely ? -**\** lol, yes, and I meant their project as a whole. -**\** lol -**\** Ok, hour is up. Anything else pressing? -**\** I don't think so - this was kinda an interim meeting because Kovri's was last week -**\** so this brings them into line -**\** next one on May 22nd, same time -**\** Ok, I'll mark the calendar. -**\** Thanks everyone. +**\** Hi fluffypony +**\** hiiii +**\** was just about to check if you're around :) +**\** Hi everyone, I think meeting-bot is still online +**\** yes it is +**\** coming through loud and clear on this side +**\* anonimal** reading backlog +**\** Hi moneromoo. +**\** Hi psi, uncrustify configs? Can you explain? +**\** uncrustify is a code styler for c/c++ +**\** I've never heard of it, plz tell me more psi? +**\** it auto formats the code +**\* psi** gets relevant links +**\** https://github.com/uncrustify/uncrustify +**\** I know that psi, but why for *.conf? +**\** i don;t understand? +**\** what about *.conf? +**\** oh anonimal +**\** not for *.conf +**\** he means conf file for uncrustify matching our coding style +**\** damn lag +**\* psi** waits to catch up +**\** fluffypony: right +**\* anonimal** back +**\** wb +**\** To answer the question, no I don't have an uncrustify config for kovri. +**\** Just a simple .vimrc. +**\** I can take a look at creating a config after #174 is resolved. +**\** fluffypony: I saw your comment in #56, what system are you runnning? +**\** anonimal: Ubuntu 14.04 +**\** and there's no Boost 1.59 / 1.60 available +**\** but that little hack worked +**\** 1.54 should work though +**\* anonimal** triple checks +**\** I can't use 1.54 +**\** incompatible with Monero +**\** monero needs .56 or higher ? +**\** .55 or higher +**\** kk +**\** so basically .59 or higher if you want both +**\** I need about 5-15 minutes to build on bsd and osx so I can open the new linkage error tickets I talked about in #174 +**\** kk +**\** :\ +**\* anonimal** the only time I have is now and a bit later but the meeting is now so I want to throw it into the topic +**\* anonimal** still compiling, should be done in 5 or so +**\** #monero-dev, FYI, our meetings have always been more organized, on-point, and I've almost always been prepared. +**\** This one caught me off guard. +**\** (last minute suggestion by fluffypony) +**\** Sorry for the wait. +**\** don't stress, ours are always by the seat of our pants +**\* anonimal** opening tickets +**\** Hmf, I need to work with the bsd a bit more before posting. +**\** Anyway, https://github.com/monero-project/kovri/issues/175 +**\** I'm only sitting with this again since I left off < 24 hours or so ago so, +**\** I haven't drawn any conclusions yet. +**\** Has anyone seen this before? #monero-dev? +**\* fluffypony** clicks +**\** moneromooo: seen anything like that before ? +**\** "Undefined symbols for architecture x86_64" +**\** The usual 'Undefined symbols for architecture x86_64' has been an osx complaint on this machine in the past. +**\** Not as such. I've seen plenty of really annoying linking issues though. +**\** this is gcc on OS X tho, right ? +**\** fluffypony: Yes. +**\** maybe we're chasing our tails on that +**\** I don't have time to deal with clang. If we want multi-distro builds, I need to streamline our process. +**\** for macosx, clang won't build because it doesn't like the things I did for the reseed rewrite and, +**\** I don't have time to keep-up with llvm development. +**\** So, thoughts? +**\** rewrite everything in C :-P +**\** lol +**\** ok my suggestion is that we eschew OS X / BSD compatibility for the moment +**\** until we can fix Clang support +**\** Thanks moneromoo. I'm glad this isn't just a kovri thing. +**\** rather than trying to fudge it +**\** Well that's the problem, this won't be the only issue. +**\** yeah I know +**\** And I'll end up wasting time juggling compilers instead of working on other things. +**\** I mean that can be a later piece of work +**\** let's focus on getting it working on one Linux and Windows, where we're running gcc and it's fine +**\** fluffypony: what part will be the later piece of work? +**\** anonimal: fixing Clang incompatibilities +**\** I don't use OSX btw, so kinda ignore what I said above. +**\** Ok sounds great, I'll focus on linux/win building. +**\** Should we remove osx/bsd build instructions from BUILDING.md? +**\** Or I'll just open the bsd ticket and maybe someone will see it? +**\** yeah, I think let's make a note that it's broken on OS X / BSD for the moment, and that contributors are welcome to fix +**\** kk +**\** Ok, I'll add the note. +**\** Any other questions/comments on #175? +**\** no not yet +**\** I mean no not atm, lol +**\** Ok, I'll add a note in #174 about what we discussed. +**\** And part 1) in #174, apparently there is an env variable I can set to get it to work. +**\** Not the first travis issue I've had to deal with. +**\** Oh well, they are growing quite nicely IMHO. +**\** travis issues are growing quite nicely ? +**\** lol, yes, and I meant their project as a whole. +**\** lol +**\** Ok, hour is up. Anything else pressing? +**\** I don't think so - this was kinda an interim meeting because Kovri's was last week +**\** so this brings them into line +**\** next one on May 22nd, same time +**\** Ok, I'll mark the calendar. +**\** Thanks everyone. **\** thank you \ No newline at end of file