| 00:53 | Bertl | off to bed now ... have a good one everyone!
|
| 00:53 | Bertl | changed nick to: Bertl_zZ
|
| 03:43 | RexOrCine | changed nick to: RexOrCine|away
|
| 08:27 | BAndiT1983|away | changed nick to: BAndiT1983
|
| 09:05 | BAndiT1983 | changed nick to: BAndiT1983|away
|
| 09:27 | BAndiT1983|away | changed nick to: BAndiT1983
|
| 11:06 | BAndiT1983 | changed nick to: BAndiT1983|away
|
| 11:29 | se6ast1an | good day
|
| 13:07 | BAndiT1983|away | changed nick to: BAndiT1983
|
| 13:32 | metal_dent[m] | joined the channel |
| 14:00 | BAndiT1983 | changed nick to: BAndiT1983|away
|
| 14:56 | metal_dent[m] | Hello, everyone! I'm Priya, an undergraduate majoring in computer science. I am interested to work on AXIOM remote for gsoc 2020. I'm a beginner so please guide me :)
|
| 15:01 | se6ast1an | hi metal_dent[m]
|
| 15:01 | se6ast1an | great, welcome!
|
| 15:02 | se6ast1an | have you read the gsoc related pages already on the apertus wiki, etc.?
|
| 15:12 | metal_dent[m] | Yes and also I've gone through the C/C++ challenge
|
| 15:14 | se6ast1an | great so you should already have a good overview
|
| 15:15 | se6ast1an | do you have any questions or things you want to learn more about?
|
| 15:18 | metal_dent[m] | Not right now, first let me have a look at the code properly then I'll let you know :)
|
| 15:25 | se6ast1an | great, please do
|
| 15:35 | Bertl_zZ | changed nick to: Bertl
|
| 15:35 | Bertl | morning folks!
|
| 15:38 | BAndiT1983|away | changed nick to: BAndiT1983
|
| 15:39 | se6ast1an | good day
|
| 15:52 | gsalazar | joined the channel |
| 16:01 | gsalazar | vup: sorry for the late reply, the main pro's for an approach like yocto buildroot is the possibility to strip down the rootfs and the guarantee that the distributed setup is always the same both build systems generate a *nix based system and can integrate with update mechanisms for customers. For development, yocto can generate an SDK that ensures that everyone is running the same toolchain and it can also integrate with qemu.
|
| 16:03 | Bertl | yeah, but let's say you just got an AXIOM Dev Kit to quickly prototype something, and you need a typical unix tool which we didn't include because it wasn't required ...
|
| 16:05 | Bertl | would you prefer to install a huge SDK, build a new rootfs for hours, write it to the SD card just to find out that you need a newer version or a different tool, or would you rather want to use the package manager to simply install it from the internet? :)
|
| 16:14 | metal_dent[m] | I'm a little confused, for the task should clone and build axiom remote or axiom beta firmware?
|
| 16:17 | BAndiT1983 | metal_dent[m]: which task do you want to apply to?
|
| 16:18 | metal_dent[m] | BAndiT1983: Task 1 of C/C++ challenge (Add DrawIcon() in Painter)
|
| 16:19 | metal_dent[m] | For the project AXIOM Remote
|
| 16:19 | BAndiT1983 | your last line summarizes my answer
|
| 16:19 | BAndiT1983 | axiom remote is a standlaone device, which would control the camera via usb
|
| 16:20 | metal_dent[m] | > your last line summarizes my answer
|
| 16:20 | metal_dent[m] | okay, cool 😅
|
| 16:34 | gsalazar | Bertl: that's one of the downsides for it, but it avoids the whole "but it works in my machine" type of issues and for customer deployment it can make things easier. Maybe it does not make sense for right now but it might be something to consider
|
| 16:36 | Bertl | let's split the 'customer' part into 'end user' and 'developer' because they have very different use cases
|
| 16:37 | Bertl | I totally agree that we want a tightly controlled environment for the 'end user' where there is no discussion what software/version is running on the camera
|
| 16:38 | Bertl | but for the typical development/prototyping case, a 'build system' like yocto would be mostly 'in the way of getting work done'
|
| 16:39 | Bertl | and once the 'customer' builds their own rootfs, we also lost the small advantage you describe
|
| 16:42 | gsalazar | for prototyping I agree it can sometimes get in the way of getting things done but for development it really ensures a coherent development environment between all developers and also for packaging it for end users, they can download a prebuilt package and don't necessarily need to build it.
|
| 16:42 | gsalazar | in terms of adding a tool for development you can also just add it by copying the binary to the target to see if it suits your needs or not before actually packaging it in the final image
|
| 16:45 | gsalazar | left the channel |
| 16:45 | Bertl | I've had quite some encounters with yocto (and similar tools) and those are really nice if you have a stable system with a well known set of tools/packages where you add or remove one every year
|
| 16:47 | Bertl | and from the developer PoV, I've always found them to be a PITA which is the reason why we went for Arch Linux on the AXIOM in the first place ... you miss a tool for a task, hook up the camera and get the package ... the package is not available? grab the sources and build them ...
|
| 16:47 | Bertl | again, this is not the case for an 'end user' camera
|
| 16:48 | Bertl | there we want to prevent the user from installing anything unless they confirm that they know what they are doing and that they are aware that those changes might affect the camera
|
| 16:54 | comradekingu | left the channel |
| 16:59 | gsalazar | joined the channel |
| 17:05 | gsalazar | left the channel |
| 17:12 | gsalazar | joined the channel |
| 17:27 | gsalazar | left the channel |
| 17:49 | vup | gsalazar: for the "but it works on my system part" we are already using docker to build everything and so far that seems to have worked fine in making assembling the firmware reproduceable
|
| 18:37 | metal_dent[m] | Is it necessary to install v2.3 of xc32 for building firmware? Can it be done using 2.1?
|
| 18:39 | se6ast1an | probably works fine as well, BAndiT1983?
|
| 18:39 | comradekingu | joined the channel |
| 18:40 | BAndiT1983 | metal_dent[m]: either version should work, we are not using anything special there
|
| 18:41 | metal_dent[m] | Okay great then cuz v2.3 is hard to find. So, I'll just change the version number in the makefile if that's okay
|
| 18:42 | BAndiT1983 | why is it hard to find? it's on the microchip site
|
| 18:43 | BAndiT1983 | https://www.microchip.com/mplab/compilers
|
| 18:45 | metal_dent[m] | yeah I found that one but it requires lots of setting-up and 2.1 is already present in the AUR 😅
|
| 18:45 | metal_dent[m] | So before going into the long process of setup I thought of asking you whether it's alright using the lower version
|
| 18:50 | BAndiT1983 | setup is also not that long, but try AUR, although i can't guarantee as many of them are not that good maintained and are maybe broken
|
| 18:51 | BAndiT1983 | setups is only a download and clicking through few dialogs, nothing else
|
| 19:23 | metal_dent[m] | okay, let me try using v2.1 if that won't work i'll do using 2.3 :)
|
| 19:42 | Bertl | off for now ... bbl
|
| 19:42 | Bertl | changed nick to: Bertl_oO
|
| 20:47 | BAndiT1983 | changed nick to: BAndiT1983|away
|
| 20:54 | gsalazar | joined the channel |
| 21:00 | gsalazar | left the channel |
| 21:12 | comradekingu | left the channel |
| 21:40 | BAndiT1983|away | changed nick to: BAndiT1983
|
| 21:57 | se6ast1an | off to bed
|
| 21:57 | se6ast1an | god night
|
| 21:57 | se6ast1an | +good
|
| 23:09 | BAndiT1983 | changed nick to: BAndiT1983|away
|
| 23:22 | comradekingu | joined the channel |
| 23:34 | abc | joined the channel |
| 23:38 | abc | left the channel |