The aarch64 packages have finished building. Can you try to use them, according to the guide? You can just do everything as the guide says (except use the environment.yml from the OpenOutlier repo, of course).

On 4/26/25 21:40, Ethan C wrote:

I am currently building aarch64 packages, I will update you if they are completed. You can check the progress on GitHub <https://github.com/ethanc8/gnustep-forge-feedstocks/actions/runs/14687506985/job/41218202112>. I don't have an aarch64 machine set up right now, so I would need you to test the packages.

On 4/26/25 20:02, Patrick Cardona wrote:
Hi Ethan,

Conda and manba seem to loook great, but as says your guide :

Right now it only works on x86_64 glibc Linux.
And I am working on aarch64. So I did not follow the conda way.

But I tried on another env with Clang already there (within NEXTSPACE: Debian 
clang version 14.0.6).

So I could build some parts and was stuck at this (I just copied the end, 
because all the errors are the same):

OOStyleRegistry.mm:348:7: note: candidate constructor (the implicit copy 
constructor) not viable: requires 1 argument, but 7 were provided
class number_style_attribute : public style_attribute
       ^
OOStyleRegistry.mm:348:7: note: candidate constructor (the implicit move 
constructor) not viable: requires 1 argument, but 7 were provided
3 warnings and 13 errors generated.
gmake[3]: *** [/Developer/Makefiles/rules.make:575: 
obj/OpenOutliner.obj/OOStyleRegistry.mm.o] Error 1
gmake[2]: *** [/Developer/Makefiles/Instance/application.make:145: 
internal-app-run-compile-submake] Error 2
gmake[1]: *** [/Developer/Makefiles/Master/rules.make:297: 
OpenOutliner.all.app.variables] Error 2
make: *** [/Developer/Makefiles/Master/application.make:38: internal-all] Error
2

Obviously due to my clang version.

On 2025-04-26 04:03:51 +0200 Ethan C<[email protected]> wrote:

Could you try my guide to installing GNUstep with Conda
<https://github.com/ethanc8/gnustep-forge-feedstocks/blob/master/guide.md>?
Use the environment.yml in the OpenOutliner repo
<https://github.com/ethanc8/OpenOutliner/blob/master/environment.yml> rather
than the one in the guide. It should have everything you need, but I've only
tested it on my machine.

Note that you always need to `mamba activate gnustep` in order to enter the
environment. This environment will contain Clang, the latest stable releases
of the GNUstep core libraries as of December, glibc 2.34, libbsd, zlib, and
all the other dependencies.

Thanks,

Ethan

On 4/25/25 17:42, Patrick Cardona wrote:
Hello Ethan and Greg,
Tried to build from the last commit of Ethan, but obviously, my GNUstep
environment (GS-Desktop by Ondrej Florian, on Debian 12, aarch64) is not
enough up to date: I am missing arc and the compiler complains:
    Compiling file AppDelegate.m ...
    gcc: error: unrecognized command-line option ‘-fobjc-arc’; did you
mean ‘-fobjc-gc’?
I installed clang, but it did not fixed this.
Are you both working on FreeBSD ?
On 2025-04-25 21:18:59 +0200 Ethan C<[email protected]> wrote:
After adding all the resources and setting the main storyboard to
Main.storyboard, it gives me an error saying that -[NSXMLDocument
initWithData:options:error] is being called with data = nil. I have just
committed this change, and I can't debug further.
On 4/25/25 13:13, Gregory Casamento wrote:
If you commit your changes (I presume you have) I'll take a look.
On Fri, Apr 25, 2025 at 2:04 PM Ethan C<[email protected]> wrote:
        After disabling the pasteboard, the app now builds and links.
        However, only the miniwindow shows up, and it complains about not
        being able to find its resources. I don't know the GNUstep
        resource system well so some help would be appreciated.
        On Fri, Apr 25, 2025, 10:10 Ethan C<[email protected]> wrote:
            Thanks Patrick, Greg!
            Hi everyone,
            I have written a GNUmakefile. The main obstacle is the
            pasteboard functionality.
            GNUstep implements the OpenStep/pre-10.5 OSX pasteboard (see
            the GNUstep docs
<https://www.gnustep.org/resources/documentation/Developer/Gui/Reference/NSPasteboard.html>
            and the Apple docs
<https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/CopyandPaste/CopyandPaste.html>);
            I have no idea how it integrates with the system's clipboards.
            This pasteboard contains a single item, which may have
            multiple representations.
            Modern macOS implements the post-10.6 OSX pasteboard (see the
            Apple docs
<https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/PasteboardGuide106/Introduction/Introduction.html#//apple_ref/doc/uid/TP40008099>
            - "Pasteboard Concepts" is the most important part), and
            OpenOutliner expects this to work. This pasteboard is a list
            of items (for example, if you copy a selection of a webpage
            which contains an image it should put a rich text and an image
            onto the pasteboard), each of which may have multiple
            representations. Additionally, it starts using Uniform Type
            Identifiers (UTIs) in order to refer to types rather than use
            the old pasteboard type strings (at least in 10.6 those old
            strings were still supported but were deprecated).
            It looks kind of complicated to implement the new pasteboard
            API, so maybe we could try porting OpenOutliner to the old
            pasteboard API or temporarily disabling all the features which
            need the pasteboard. Do any of you have opinions on this?
            The Uniform Type Identifiers framework, part of
            LaunchServices, seems to be implemented by Boron so we could
            probably do that. (However, that would make gnustep-gui depend
            on Boron, which may or may not be wanted.) We might want to
            implement in Boron the new Uniform Type Identifiers framework
<https://developer.apple.com/documentation/uniformtypeidentifiers?language=objc>
            introduced in macOS 11 Big Sur, which is object-oriented (UTIs
            are of type `UTType*` rather than `NSString*`, and it provides
            an Objective-C API). Although OpenOutliner doesn't use the new
            UTI APIs, it would be useful to implement in case newer apps
            need it, and regardless it seems to be a cleaner API.
            Thanks,
            Ethan
            On 4/25/25 08:01, Gregory Casamento wrote:
            Ethan,
            Mine is gcasa.  I would like to help a little if I can. Also,
            expanding libs-xcode, if it needs it, to handle it.
            Yours, GC
            On Fri, Apr 25, 2025 at 4:11 AM Patrick Cardona
            <[email protected]> wrote:
                On 2025-04-24 18:50:21 +0200 Ethan C
                <[email protected]> wrote:
                Hello Ethan,
                > I started on the porting at
                https://github.com/ethanc8/OpenOutliner.
                Great!
                > You can
                > grep for "FIXME-GNUstep" for the things that don't work
                yet (the whole thing
                > doesn't compile yet). If you give me your GitHub
                username I can give you
                > commit access to my fork.
                Mine is: pcardona34
                >
                > On 4/24/25 08:14, Patrick Cardona wrote:
                >> Hello Ethan,
                >
                >> Thanks for this mention. I shall look at this.
                >
                >> On 2025-04-24 04:57:47 +0200 Ethan C
                <[email protected]> wrote:
                >
                >>> Hi everyone,
                >
                >>> David Chisnall recently mentioned on Lobsters
                >>>
<https://lobste.rs/s/btjtkr/what_software_do_you_dream_about_do_not#c_i2m53u>
                >>> a clone of OmniOutliner 3 he wrote in 2017, and said
                it would be easily
                >>> portable. Its source is on GitHub
                >>><https://github.com/davidchisnall/OpenOutliner> if
                you want to look at it.
                >>>  From the README it looks like a decently complex
                application with lots
                >>> of functionality, so it could be quite useful to port
                it. See also Liam
                >>> Proven's comment about why he uses outliners
                >>>
<https://lobste.rs/s/btjtkr/what_software_do_you_dream_about_do_not#c_owdlc8>
                >>> to get an idea of what outliner users would want. I
                might take up this at
                >>> some point, but I doubt it as I am quite busy and
                have too many side
                >>> projects already :)
                >
                >>> Thanks,
                >
                >>> Ethan Charoenpitaks
                >
                >
                >
                --             Patrick Cardona - France
                MUA: GNUMail - Hardware: Raspberry Pi pi400 Model
                OS: Debian 12 (RPI-OS Lite) - Desktop: GSDE
            --         Gregory Casamento
            GNUstep Lead Developer / Black Lotus, Principal Consultant
            http://www.gnustep.org -http://heronsperch.blogspot.com
            https://www.patreon.com/bePatron?u=352392 - Become a Patron
            https://www.openhub.net/languages/objective_c
https://www.gofundme.com/f/cacao-linux-a-gnustep-reference-implementation
--
Gregory Casamento
GNUstep Lead Developer / Black Lotus, Principal Consultant
http://www.gnustep.org -http://heronsperch.blogspot.com
https://www.patreon.com/bePatron?u=352392 - Become a Patron
https://www.openhub.net/languages/objective_c
https://www.gofundme.com/f/cacao-linux-a-gnustep-reference-implementation

Reply via email to