discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Development environment


From: Ivan Vučica
Subject: Re: Development environment
Date: Wed, 13 Dec 2017 14:30:52 +0000

You could try just building on a Mac and see if the bug is reproducible.

Since your RPi3 probably runs a Linux variant, VM with a Linux distro
seems like a good plan.

If it doesn't repro, the bug might be ARM specific for some reason.

On Mon, Dec 11, 2017 at 3:10 PM, Daniel Santos <address@hidden> wrote:
> Now replying to the list
>
> ---------- Forwarded message ----------
> From: Daniel Santos <address@hidden>
> Date: Mon, Dec 11, 2017 at 3:09 PM
> Subject: Re: Development environment
> To: Ivan Vučica <address@hidden>
>
>
> For now I am interested in GNUMail. I am running gnustep in a raspberry pi
> 3, and will do the bug fixing on a VM in a mac, and then test it on the VM
> and then the pi.
> I don't have any specific bug identified yet, for now I want to build
> everything from source so I get the latest versions of everything.
>
> This is because the first thing I encountered in GNUMail was strings not
> displaying in the UI. I had to click the email headers to see them. So I
> figured that building everything from source might eliminate that problem. I
> have built the latest GNUMail and it has that problem, so I figure the
> problem could be in one of the underlying libs (cairo ?)
>
>
> On Mon, Dec 11, 2017 at 1:49 PM, Ivan Vučica <address@hidden> wrote:
>>
>> Adding discuss-gnustep@ again.
>>
>> pon, 11. pro 2017. u 11:09 Daniel Santos <address@hidden> napisao
>> je:
>>>
>>> Ok. Here's the motivation for the question. I want to fix bugs in the
>>> code. What is the best toolchain for doing this ? (I have access to osX,
>>> Linux and windows boxes)
>>
>> Fix bugs in which code? GNUstep? Third party GS apps? Your apps?
>>
>> You should certainly fix them on the platform you intend to run the code
>> on. Windows and *nix builds of GNUstep will branch differently for very
>> obvious reasons, while on macOS you can force GNUstep into being built into
>> your binary, it's just not something we suggest being done.
>>
>> In your other email it sounds like you want to fix apps. First choice is
>> "where will these apps be running"? If the answer is "freebsd", use freebsd.
>> If it's "linux", use Linux. If it's Mac, use Mac along with Apple
>> frameworks.
>>
>> For non-Apple platforms, it's best to write GNUmakefiles that make use of
>> gnustep-make helper scripts and forget Xcode is there. We have a tool to
>> build Xcode projects, but it's not going to help you modify them. We have an
>> IDE (ProjectCenter) which doesn't know about Xcode project files, and I
>> personally find myself more productive if I don't use it. Other people like
>> it.
>>
>> Which applications do you want to fix? Do you have specific bugs you want
>> to fix? Can we help you get started with a specific task?
>> --
>> Sent from Gmail Mobile on iPad
>
>
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnustep
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]