**** BEGIN LOGGING AT Wed May 05 02:59:56 2021
May 05 06:38:47 <DhruvaG2000[m]> Gentle Reminder fellow students and mentors: Today Meet @ 10:00 PM IST,  9:30 AM US Pacific,  12:30 PM US Eastern.
May 05 17:35:55 <cwicks[m]> Hello mentors and students!
May 05 17:36:07 <cwicks[m]> I hope everyone is feeling well?
May 05 17:36:34 <ArchismanDey[m]> Hello everyone!
May 05 17:36:45 <satacker[m]> Hi 👋
May 05 17:37:34 <OmkarBhilare[m]> Hi everyone
May 05 17:38:10 <satacker[m]> Hello Arthur Sonzogni [this](https://pastebin.com/TaAAPasC) is the traceback for built of print key press example , i also noticed that all those examples with interactive screen had the same build issue.
May 05 17:40:03 <pratimu[m]> Hi all
May 05 17:40:51 <jduchniewicz> hello!
May 05 17:41:49 <ArthurSonzogni[m> <satacker[m] "Hello Arthur Sonzogni [this](ht"> I recently merge mouse support branch. Maybe the continuous-integration didn't catch the build issues you are seeing?
May 05 17:42:14 <lorforlinux[m]> Hey everybody, I hope all are doing great :)
May 05 17:43:12 * ArthurSonzogni[m  < https://matrix.org/_matrix/media/r0/download/matrix.org/amJUTQyzKxdrAXIOXWvXlaBi/message.txt >
May 05 17:44:56 * satacker[m]  < https://matrix.org/_matrix/media/r0/download/matrix.org/npuKlAgSgZHVzNppSzkcyuVm/message.txt >
May 05 17:45:45 <satacker[m]> by deciding arch i meant the proper structure for frontend and backend
May 05 17:49:04 <Willmish[m]> Hi!
May 05 17:49:21 <ArthurSonzogni[m> <satacker[m] "> <@arthursonzogni:matrix.org> C"> It's up to you. It is usually easier to share early repository to collaborate.
May 05 17:52:03 * satacker[m]  < https://matrix.org/_matrix/media/r0/download/matrix.org/dQZDRXOrfgodvyIICwBCFqzD/message.txt >
May 05 17:52:04 <ArthurSonzogni[m> However this only explain the warning, not the error.
May 05 17:52:55 <ArthurSonzogni[m> <satacker[m] "> <@arthursonzogni:matrix.org> I"> Okay great!
May 05 17:56:53 <ArchismanDey[m]> *built gcc-pru and simppru from source, and figuring out how to make simppru emit the generated C code and not just the final output file
May 05 17:59:53 <ArchismanDey[m]> <ArchismanDey[m] "*built gcc-pru and simppru from "> vedant16
May 05 18:02:54 <DhruvaG2000[m]> Hey I have added BelaAI enumeration and committed to the repo, also added a few lines of code to add belaAI in the conditional statements.
May 05 18:02:54 <DhruvaG2000[m]> Requesting giuliomoro / giuliomoro[m]  to check out the gsoc beagle forum and answer a few doubts that I have posted
May 05 18:03:56 <DhruvaG2000[m]> I have also started writing a blog where I am trying to cover BBAI essentials based on derek molloy's guide ( just that he wrote everything for bbb, I am writing for BBAI using the TRM)
May 05 18:04:21 <OmkarBhilare[m]> Patryk Mężydło (He had done BeagleWire related project in GSoC 2017) joined qwerty discord server, he also reviewed my proposal and gave some points.
May 05 18:04:21 <OmkarBhilare[m]> as of now my few exams are left but side by side I'm reading litedram docs and also started to implement it on the upduino board.
May 05 18:04:21 <OmkarBhilare[m]> m_w
May 05 18:04:35 <OmkarBhilare[m]> My last exam is on friday, after that I will speed up the pre work.
May 05 18:06:33 <vedant16[m]> Hi everyone :)
May 05 18:06:57 <vedant16[m]> <ArchismanDey[m] "vedant16"> isn't generated C code and file file the same thing ?
May 05 18:07:04 <vedant16[m]> do you wants hints ;)
May 05 18:08:18 <DhruvaG2000[m]> <ArchismanDey[m] "*built gcc-pru and simppru from "> Hey you already have a beaglebone?
May 05 18:08:37 <vedant16[m]> compiling simppru doesn't need beagle
May 05 18:09:05 <DhruvaG2000[m]> Oh okay
May 05 18:09:34 <ArchismanDey[m]> <vedant16[m] "isn't generated C code and file "> basically I wanted an option like simppru -c test -o test that gives the C file test.c printed by code_printer.h along with test.sim which is generated after compiling test.c using pru-gcc
May 05 18:09:44 <jduchniewicz> compiling anything usually does not require the target hw
May 05 18:09:50 <jduchniewicz> just the toolchains
May 05 18:10:32 <ArchismanDey[m]> also dump the generated C file if we supply --verbose maybe
May 05 18:11:35 <vedant16[m]> <ArchismanDey[m] "basically I wanted an option lik"> Wait, I am confused now, test.sim is the source file
May 05 18:11:57 <vedant16[m]> test.sim -> test.c -> test.pru0 (firmware)
May 05 18:12:25 <ArchismanDey[m]> <vedant16[m] "Wait, I am confused now, test.si"> I meant test.pru0* instead of test.sim
May 05 18:13:15 <ArchismanDey[m]> <vedant16[m] "test.sim -> test.c -> test.pru0 "> and there is currently no way to get the test.c file directly right?
May 05 18:13:31 <vedant16[m]> <ArchismanDey[m] "I meant test.pru0* instead of te"> Ok, understood.
May 05 18:14:44 <vedant16[m]> <ArchismanDey[m] "and there is currently no way to"> There is a way. it's not direct.
May 05 18:14:54 <ArchismanDey[m]> I should go through CMake docs more properly
May 05 18:15:13 <vedant16[m]> but you can read the generated .c file easily. Find it, will be a good exercise to read the code.
May 05 18:15:21 <DhruvaG2000[m]> Looks like giuliomoro isn't really there on element so any messages of the past he probably isn't able to see ?
May 05 18:15:47 <YadnikBendale[m]> Hello,I have setup the zephyr sdk on my linux machine following all the steps given here-https://docs.zephyrproject.org/latest/guides/beyond-GSG.html. I had one doubt, for the porting process, what do I have to do after building for QEMU?
May 05 18:15:54 <vedant16[m]> I mean, simppru creates a temp .c file somewhere, look in the source code for the location.
May 05 18:16:00 <vedant16[m]> lemme know if you find it ;)
May 05 18:16:13 <jduchniewicz> <YadnikBendale[m] "Hello,I have setup the zephyr sd"> you can run it in qemu
May 05 18:16:41 <vedant16[m]> But, I got your point, you can add -c thing, it is useful.
May 05 18:16:44 <jduchniewicz> any example from the zephyr examples
May 05 18:16:53 <ArchismanDey[m]> <vedant16[m] "but you can read the generated ."> yes, I was reading the code but basically I'm not familiar with the details of CMake so I have started reading CMake docs
May 05 18:17:37 <vedant16[m]> but then you need to make sure simppru, can also take this .c file and make a binary.
May 05 18:17:48 <jduchniewicz> cmake is REALLY not user friendly (even makefiles are better) so I wish you a lot of patience :)
May 05 18:18:03 <ArchismanDey[m]> <vedant16[m] "But, I got your point, you can a"> Yeah, I was planning to do this
May 05 18:18:05 <vedant16[m]> <ArchismanDey[m] "yes, I was reading the code but "> Good, let me know if anything comes up. To look for source code, start with main.c
May 05 18:18:21 <vedant16[m]> and try to go one by one into the functions.
May 05 18:18:38 <vedant16[m]> <jduchniewicz "cmake is REALLY not user friendl"> I disagree
May 05 18:18:57 <vedant16[m]> CMake is really good, from my experience using it.
May 05 18:19:11 <vedant16[m]> I found meson, a nuisance as compared to it.
May 05 18:19:17 <satacker[m]> <jduchniewicz "cmake is REALLY not user friendl"> why prefer writing targets when we can automate it?
May 05 18:19:31 <jduchniewicz> first problem is that it does not have good documentation
May 05 18:19:40 <jduchniewicz> nevermind, did not want to spark a discussion
May 05 18:20:17 <vedant16[m]> <jduchniewicz "nevermind, did not want to spark"> no problem, discussions are always welcome.
May 05 18:20:27 <vedant16[m]> but it does have loads of docs on the internet.
May 05 18:20:51 <vedant16[m]> <satacker[m] "why prefer writing targets when "> true
May 05 18:20:56 <ArchismanDey[m]> <vedant16[m] "but then you need to make sure s"> Yes, but just dumping the C file would be a nice first step
May 05 18:21:39 <jduchniewicz> it took me a lot of time get to grips with cmake files (maybe I do not speak good devops :)
May 05 18:21:51 <jduchniewicz> *to
May 05 18:21:55 <vedant16[m]> I found this: https://cliutils.gitlab.io/modern-cmake/
May 05 18:22:03 <vedant16[m]> very very useful when I learnt it.
May 05 18:22:56 <vedant16[m]> <ArchismanDey[m] "Yes, but just dumping the C file"> okay, a hint. check main.c main() function.
May 05 18:23:02 <vedant16[m]> you'll find the generated .c file
May 05 18:23:09 <DhruvaG2000[m]> is there by any chance a way to test overlays without having the actual devices?
May 05 18:23:09 <DhruvaG2000[m]> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-BONE-AUDI-02-00A0.dts
May 05 18:23:09 <DhruvaG2000[m]> Wanted to check this out
May 05 18:23:29 <jduchniewicz> how broad is usage of cmake in BB community? it would be nice to have standard cmake templates which allow for easy cloning and reusing
May 05 18:23:58 <jduchniewicz> my main issue with cmakes is that there is no out of the box solution given to you and this makes the entry level quite high
May 05 18:24:41 <jduchniewicz> I remember when migrating from vs build system to building bigger projects on linux and using Makefiles with cmake I was in for a surprise
May 05 18:24:56 <ArchismanDey[m]> Oh, it's just in /tmp/temp.c
May 05 18:25:12 <jduchniewicz> and a multitude of dubious documents without one: do this in this and that way
May 05 18:25:19 <vedant16[m]> <jduchniewicz "how broad is usage of cmake in B"> people here use autotools, which is real pain to use.
May 05 18:25:23 <jduchniewicz> and it is not only me
May 05 18:25:35 <jduchniewicz> oh autotools :/
May 05 18:26:41 <vedant16[m]> autotools is real bad. I used it in my gsoc project. struggled for 4 days, and then shifted to cmake. BOom finished in 1 day
May 05 18:27:07 <jduchniewicz> yeah, cmake gets the job done
May 05 18:27:18 <jduchniewicz> not advocating Rust, BUT :)
May 05 18:27:36 <jduchniewicz> it just bought me with the build system and cargo
May 05 18:28:21 <ArchismanDey[m]> <jduchniewicz "and a multitude of dubious docum"> flexibility vs readability trade-off
May 05 18:28:24 <jduchniewicz> assuming you just want to get the job done and not devops it, having an out of the box solution is pleasant
May 05 18:29:07 <vedant16[m]> <jduchniewicz "it just bought me with the build"> but cargo is pretty brittle.
May 05 18:29:10 <jduchniewicz> you can achieve flexibility by being concise and just mentioning the various options
May 05 18:29:17 <vedant16[m]> with cmake you can do every language afaik
May 05 18:29:32 <vedant16[m]> also, I helps when you have more than one compiler.
May 05 18:29:45 <vedant16[m]> it*
May 05 18:29:50 <jduchniewicz> yes it is quite good with that
May 05 18:30:11 <vedant16[m]> you can try meson or bazel
May 05 18:30:29 <vedant16[m]> <ArchismanDey[m] "flexibility vs readability trade"> see the issue is, older cmake was terrible.
May 05 18:30:37 <vedant16[m]> newer variants are pretty good.
May 05 18:30:57 <vedant16[m]> as for templates here: https://project-awesome.org/onqtam/awesome-cmake
May 05 18:30:58 <jduchniewicz> anyway, my take on this is: have a good starting point or place in BB wiki(github) which is maintained and offers the cmake files
May 05 18:31:28 <vedant16[m]> fair enough
May 05 18:31:53 <jduchniewicz> so for example people in this year's edition can just not scratch their heads too much and get to work
May 05 18:32:15 <jduchniewicz> basically that is what I do with makefiles and cmake recipies for the projects I do
May 05 18:32:35 <jduchniewicz> just tweaking them if I need anything non-standard
May 05 18:33:05 <jduchniewicz> yeah ./rand --end
May 05 18:33:08 <jduchniewicz> *rant
May 05 18:33:47 <jduchniewicz> thanks for the document, did not know about it
May 05 18:35:34 <ArchismanDey[m]> Yes, the introduction to Modern CMake seems useful
May 05 18:44:37 <vedant16[m]> <jduchniewicz "thanks for the document, did not"> git revert rant-commit ?
May 05 18:44:43 <vedant16[m]> xD
May 05 18:48:45 <jduchniewicz> nah, the rant remains there. Probably will never love CMake, but it is what is is and we have to make the most of it
May 05 18:49:05 <jduchniewicz> as you said, meson's and bazel's and other are much worse to use
May 05 18:49:23 <jduchniewicz> maybe ninja (is it alive though?)
May 05 18:50:13 <DhruvaG2000[m]> <jduchniewicz "maybe ninja (is it alive though?"> Yes yes
May 05 18:50:26 <DhruvaG2000[m]> ESP IDF uses ninja
May 05 18:58:24 <vedant16[m]> <jduchniewicz "maybe ninja (is it alive though?"> Ninja is a intermediate step
May 05 18:58:33 <vedant16[m]> its equivalent to make
May 05 18:58:42 <vedant16[m]> cmake generates -> make or ninja
May 05 18:58:52 <vedant16[m]> FYI, cmake is a turing complete language
May 05 19:01:43 <nerdboy> cmake is kinda opaque/painful when it isn't done well
May 05 19:02:54 <nerdboy> turns out to be a good tool for cross-platform/multi-os python extension pkgs
May 05 19:07:44 <jduchniewicz> maybe my look at CMake is flawed after having to fix many poorly written ones several years ago :)
May 05 19:08:02 <nerdboy> that would do it...
May 05 19:08:08 <jduchniewicz> much as I like flexibility, it can be abused and make life painful
May 05 19:08:33 <jduchniewicz> reasoning akin to Linus and C language
May 05 19:08:53 <jduchniewicz> and his love for C++
May 05 19:21:17 <YadnikBendale[m]> <jduchniewicz "any example from the zephyr exam"> I am following this https://github.com/micropython/micropython/blob/master/ports/zephyr/README.md
May 05 19:23:11 <YadnikBendale[m]> I am trying from here https://docs.zephyrproject.org/1.9.0/boards/arm/qemu_cortex_m3/doc/board.html
May 05 19:23:41 <YadnikBendale[m]> jduchniewicz: Can you please have a look and see if I am proceeding in right direction.
May 05 19:58:30 <ds2> cmake is just downright evil
May 05 19:58:42 <ds2> config.h works
May 05 22:48:58 <nerdboy> i think it's just One of Those Things
May 05 22:50:59 <nerdboy> first i learned to like make...  then i learned to like autotools (excluding libtool)...  then i eventually learned to like cmake (mainly for CI/distributing python extensions)...
May 05 22:52:02 <nerdboy> now it's time to watch my latest kernel blow chunks
**** ENDING LOGGING AT Thu May 06 02:59:56 2021