Re: qcontrol development
Looks like that qemubuilder doesn't support arm kernel, though.
http://wiki.debian.org/qemubuilder
I have setup the following solution:
- Xcode on my iMac to create source code (syntax highlighting and
basic compiling!)
- ssh script to transfer source code to armel vm and to build
remotely, than transfer the executable to QNAP device.
This works pretty well, Xcode can even compile the source code.
Intellisense is also working.
Transferring and compiling the source code takes about 2
minutes...well makes you more alert to review your code before
building it...
Gr. Bas.
On Sat, Mar 12, 2011 at 11:21 PM, Bas Delfos <b.delfos@gmail.com> wrote:
> Hi Benoît,
>
> Thanks for the tip.
> I already found qemu and have an armel image running.
> My other debian system where i run qemu on is very old. Running a vm
> is a solution for building sources only, because the performance is on
> the slow side.
>
> I will look into qemubuilder, i suspect it is easier and probably
> faster than running a vm.
>
> Bas.
>
> 2011/3/12 Benoît Knecht <benoit.knecht@fsfe.org>:
>> Hi Bas,
>>
>> Bas Delfos wrote:
>>> I also have an old P4 running squeeze on it, can i some how build the
>>> qcontrol executable on an i386 with another target architecture?
>>> Because I already build the last sources of qcontrol on the P4, but
>>> the executable doesn't run on the QNAP (I have the build param -aarmel
>>> specified)?
>>
>> I'm sure there are many other solutions, but what has worked best for me
>> so far is qemubuilder. It runs a complete debian armel system in qemu
>> and compiles your package there. Once you have a dsc file for your
>> software, it's as simple as running
>>
>> $ qemubuilder --build yourpackage.dsc
>>
>> Hope this helps.
>>
>> --
>> Benoît Knecht
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>> Archive: [🔎] 20110312122448.GA15610@debian.lan">http://lists.debian.org/[🔎] 20110312122448.GA15610@debian.lan
>>
>>
>
Reply to: