1

Topic: Raspberry Pi dev device.

It is necessary to collect mine Sciter for Raspberry Pi... As far as I understand it is necessary to do it true Linux way - to collect it on target the device. It is alternatively possible to try cross-compiling, but as far as I understand it works only for simple cases. Or I am mistaken? Therefore the question on Raspberry Pi dev device what it should be, for example SSD is necessary or not? Generally who has a practical experience of development under Raspberry Pi or something similar how it correctly to do?

2

Re: Raspberry Pi dev device.

Hello, c-smile, you wrote: CS> It is necessary to collect mine Sciter for Raspberry Pi... CS> As far as I understand it is necessary to do it true Linux way - to collect it on target the device. The normal method of the assembly  for this sort of boards is cross-compilation. The assembly on the device it can stress-test for check that you a kernel are correct  or still what need, but to use it for development CS> it is alternatively possible to try cross-compiling, but as far as I understand it works only for simple cases. Or I am mistaken? From what suddenly, esteem about openembbed/yocta/buildroot all system entirely collect cross-compilation. CS> therefore the question on Raspberry Pi dev device what it should be, for example SSD is necessary or not? CS> Generally who has a practical experience of development under Raspberry Pi or something similar how it correctly to do? Raspberry Pi dev device it is modern amd64 the computer with a heap of kernels, storages and ssd a disk.

3

Re: Raspberry Pi dev device.

Hello, c-smile, you wrote: CS> Therefore the question on Raspberry Pi dev device what it should be, for example SSD is necessary or not? , there on mine, the interface for drives misses generally. A flash card, and all. At me truth RPI2, I and actually did not reach while with it , once launched and postponed CS> Generally at whom there is a practical experience of development under Raspberry Pi or something similar how it correctly to do? Under RPI wrote nothing, but generally wrote a cross connect-platform for vindov/linoksov/bsd. In the core all did under Windows, debugged  parts using CodeBlocks, the project was without  and other. Still there was a project under any  on , normally all was written under Windows,  was code sourcery gcc or somehow so, it like was bent, but not an essence, their others is. It was written under Windows, it was debugged in qemu arm linux, final tests on  were run Anything especial. And RPI is normal arm-linux, there from all singularities only ports GPIO, and all

4

Re: Raspberry Pi dev device.

Hello, c-smile, you wrote: CS> Generally who has a practical experience of development under Raspberry Pi or something similar how it correctly to do? I normally develop and I debug the program on the big computer, and only right at the end I collect on Raspberry Pi. I collect on the device without any cross-compilations. For this purpose it is necessary to install gcc and developer libraries. Probably if it is frequent it to be engaged, it is possible to wipe a hole in a flash card. I yet did not wipe.

5

Re: Raspberry Pi dev device.

Hello, c-smile, you wrote: CS> Generally who has a practical experience of development under Raspberry Pi or something similar how it correctly to do? I collect on the big computer the programs for Raspberry. Because: (1) them it is necessary  often, after each editing, (2) scripts of the assembly itself wrote, and (3) they do not pull 100500 dependences on libraries. And a kernel, because painfully big and at it with assembly scripts precisely everything is all right. Opensorsnye things which it is necessary , something twisting, I collect on most Raspberry. Because cross-compilation it is in words good, and in practice not so. Raspberry Pi dev device it is simple the third Raspberry with heat sinks and not the cheapest microSD. SSD does not add speed, rests in USB 2.0. PS: do not contact  and other left distribution kits which ostensibly work on Raspberry. Regular Raspbian your all.

6

Re: Raspberry Pi dev device.

Hello, alpha21264, you wrote: A> Hello, c-smile, you wrote: CS>> Generally who has a practical experience of development under Raspberry Pi or something similar how it correctly to do? A> I normally develop and I debug the program on the big computer, A> and only right at the end I collect on Raspberry Pi. A> I Collect on the device without any cross-compilations. A> for this purpose it is necessary to install gcc and developer libraries. A> probably if it is frequent it to be engaged, it is possible to wipe a hole in a flash card. A> I yet did not wipe. Well in general to what such I also came. Though everyones success story force down with  every time: https://hackaday.com/2016/02/03/code-cr … pberry-pi/ But as a rule in each such article there is something of type of it: Assuming all goes well, enter the following command and you should see output similar to... That optimism not ...

7

Re: Raspberry Pi dev device.

Hello,/aka/, you wrote: A> I Collect on the big computer the programs for Raspberry. Because: (1) them it is necessary  often, after each editing, (2) assembly scripts itself wrote, and (3) they do not pull 100500 dependences on libraries. And a kernel, because painfully big and at it with assembly scripts precisely everything is all right. What is written on a C on  gathers in comparable with  a host on which 12 Gb of the RAM and a little  percents Here Java and all JVM `  great shamanism is. A> Opensorsnye of a thing whom it is necessary , something twisting, I collect on most Raspberry. Because cross-compilation it is in words good, and in practice not so.  cross-compilation also is  for allows not  to that at you on a direct system and that at you on a host. It is banal, the same plug-in to Vim - YouCompleteMe on a host gathers , and on  the third gathers  A> Raspberry Pi dev device it simply Raspberry with heat sinks and not the cheapest microSD. SSD does not add speed, rests in USB 2.0. A> PS: do not contact  and other left distribution kits which ostensibly work on Raspberry. Regular Raspbian your all.  unless not same Debian with the added repositories for  fire wood with licenses distinct from others?

8

Re: Raspberry Pi dev device.

Hello, c-smile, you wrote: CS> Therefore the question on Raspberry Pi dev device what it should be, for example SSD is necessary or not? Any, is better Pi3 CS> Generally at whom there is a practical experience of development under Raspberry Pi or something similar how it correctly to do? There are two methods: 1. On a device. Here especially problems are not present. 2.  under Raspbian with x86 on arm. For a compilation cross connect there are two methods: 1 to adjust variable surroundings, to expose different , PKGCONFIG, etc., 2 will write on CMAKE a script which to adjust all for you. Anyway there will be troubles with ways to correct  and correct , correct pkgconfig to files, etc. Consider, all councils on  on the Internet resemble for simple projects, something complex should be compiled through a pain. P.S. If you want, you can to me on on soap write, I will share pair  how to simplify to itself life about a cross connect-sbrkoj.

9

Re: Raspberry Pi dev device.

Hello, Kernan, you wrote: K> There are two methods: K> 1. On a device. Here especially problems are not present. Except memory size. Here it is banal a plug-in not to collect youcompleteme,  because of shortage of storage. K> 2.  under Raspbian with x86 on arm. K> For a compilation cross connect there are two methods: K> 1 to adjust variable surroundings, to expose different , PKGCONFIG, etc., 2 will write on CMAKE a script which to adjust all for you. Anyway there will be troubles with ways to correct  and correct , correct pkgconfig to files, etc. K> Consider, all councils on  on the Internet resemble for simple projects, something complex should be compiled through a pain. It is possible to adjust also pens, but after all all is stolen to us. It is possible to use  an image in , it is possible to use crosstool-ng for generation , it is possible buildroot to collect with the help the image under the necessary board.  and buildroot ` the ohm and yocto `  is supported without a tambourine. In buildroot even for somlabs `  i.mx6ull the unit it is possible to collect an image. So complexities  are a little exaggerated, . Though, of course, I can with such tasks did not face that gather through blood, a pain and floor-mats. Throw  , not self-interest  for the sake of, and it is pure with curiosity

10

Re: Raspberry Pi dev device.

Hello, Lucky Cat, you wrote: LC> Raspbian unless not same Debian with the added repositories for  fire wood with licenses distinct from others? Official Debiana for the Raspberry is not present. It is impossible to download an official image with debian.org, only private hand-made articles. Is  rpi23-gen-image which can be made the image Debiana for the Raspberry by other machine with Debianom, but the amount necessary  in the turned out system tired me. And Raspbian works from a box. Repositories at them the, that is they  and a file grind "same Debian".

11

Re: Raspberry Pi dev device.

Hello, c-smile, you wrote: CS> Generally who has a practical experience of development under Raspberry Pi or something similar how it correctly to do? Yes, by the way, there is such piece - yocto. https://www.yoctoproject.org/https://ww … index.html It if you need to collect the whole distribution kit for any micro-computer. I tried. It even works.

12

Re: Raspberry Pi dev device.

Hello, Lucky Cat, you wrote: LC> It is possible to use  an image in , it is possible to use crosstool-ng for generation , it is possible buildroot to collect with the help the image under the necessary board.  and buildroot ` the ohm and yocto `  is supported without a tambourine. In buildroot even for somlabs `  i.mx6ull the unit it is possible to collect an image.  apprx. What of methods you used personally on RPi? And that I saw here such here recommendations much, only was then clarified that  never them used on specific . LC> So complexities  are a little exaggerated, . LC> Though, of course, I can with such tasks did not face that gather through blood, a pain and floor-mats. For hello world, yes, something should be collected through a pain more difficult. Fresh OPS  only through dances with a tambourine.

13

Re: Raspberry Pi dev device.

Hello, Kernan, you wrote: K> 1. On a device. Here especially problems are not present. A question purely with curiosity, the assembly in the docker the container did not try? https://hub.docker.com/r/raspbian/jessie/

14

Re: Raspberry Pi dev device.

Hello, c-smile, you wrote: CS> Generally who has a practical experience of development under Raspberry Pi or something similar how it correctly to do? I such was engaged. Tried all methods." Correct "depends on the task. If once to collect and forget, it is possible directly on a target platform if development with debugging is necessary, optimization and depositing of editings a cross connect compilation will be faster. I needed month to transfer the project on ARM, but at me a heap of libraries, type Boost, Qt, websocket, a multithreading, operation with USB and serial ports... Finally came to that wrote hands general-purpose Makefile' for a cross connect of compilation which depending on the specified target platform select those or other options from connected files. It turned out so: under Windows it is launched virtual box in which the system under a specific platform then in this system   the directory with source codes and directly in this directory is launched compilation is installed and adjusted. Convenience that under each target platform we have the special virtual machine with completely adjusted cross-tools a chain. Such virtual machine it is possible , to transfer on other computer that in the conditions of command operation saves a lot of time.

15

Re: Raspberry Pi dev device.

Hello, B0FEE664, you wrote: BFE> It turned out so: under Windows it is launched virtual box in which the system under a specific platform then in this system   the directory with source codes and directly in this directory is launched compilation is installed and adjusted. Not clearly that means. virtual box allows to launch i86/x64 systems. But there and then ARM architecture. Or I that did not understand?

16

Re: Raspberry Pi dev device.

Hello, c-smile, you wrote: BFE>> It turned out so: under Windows it is launched virtual box in which the system under a specific platform then in this system   the directory with source codes and directly in this directory is launched compilation is installed and adjusted. CS> it is not clear that means. virtual box allows to launch i86/x64 systems. But there and then ARM architecture. Or I that did not understand? Yes, it I not clearly expressed. I use a cross connect compilation, i.e. on architecture i86/x64 I create  which is launched on ARM to a platform. Processors ARM differ on the architecture. For each model of the processor there is a procedure a cross connect of compilation which, as a rule, is provided with diligence of the vendor of the processor. To install and adjust on one system some tools for a compilation cross connect it is possible, but it is difficult to confuse easily also them, they can clash. In system installed in virtual box I install and I adjust tools compilations necessary for a cross connect under specific system working on specific model ARM. I.e. if on a system provider site it is written that they recommend to use, say, Ubuntu such version we take this Ubuntu the specified version and we install it in Virtual Box. Then downloads and we adjust compilations recommended for a cross connect tools in this separate virtual machine. In the same virtual machine we install and we compile by means of the installed tools of compilation of library which are necessary to us for our programs. After end of these procedures it is possible to compile own source codes. Here somehow so.

17

Re: Raspberry Pi dev device.

Hello, alpha21264, you wrote: A> and only right at the end I collect on Raspberry Pi. And what for you generally do it? Than the cross connect-compiled an executed file is bad?

18

Re: Raspberry Pi dev device.

c-smile: CS> Generally who has a practical experience of development under Raspberry Pi or something similar how it correctly to do? Specially for a raspberry professionally did not develop, but in due time pottered with adjustments much. Except enumerated above in a branch, I can prompt two more methods: 1. Foreign debootstrap. In some directory on a host x86 (or x64) the distribution kit  ARM, compatible to a raspberry is installed.  work through qemu-user. The method on expenses is comparable with the cross-compiler assembly, but can be sometimes more convenient. 2. To launch the raspberry emulator through qemu-system, and from it to collect. , easier, than with wires to potter.

19

Re: Raspberry Pi dev device.

Hello, Kernan, you wrote: K> Hello, Lucky Cat, you wrote: LC>> It is possible to use  an image in , it is possible to use crosstool-ng for generation , it is possible buildroot to collect with the help the image under the necessary board.  and buildroot ` the ohm and yocto `  is supported without a tambourine. In buildroot even for somlabs `  i.mx6ull the unit it is possible to collect an image. K> Ok apprx. Whom of methods you used personally on RPi? And that I saw here such here recommendations much, only was then clarified that  never them used on specific . Was specific for RPi3 buildroot, yocto and QEMU/debootstrap I used personally. So it is not necessary pathetics. I can and I do not launch colliders on , but  under the tasks used. Without a pain and a floor-mat. LC>> so complexities  are a little exaggerated, . LC>> Though, of course, I can with such tasks did not face that gather through blood, a pain and floor-mats. K> for hello world, yes, something should be collected through a pain more difficult. Fresh OPS  only through dances with a tambourine. If that that becomes through a pain can not that method. And some things except as cross-compilation do not collect.