but it compiles!

I'm looking through this article https://ashes999.github.io/learnhaxe/animated-gifs-in-haxeflixel.html, and one of the steps says

Update Project.xml and add . This will tell lime to process your gif files as binary, so you can load them via Assets.getBytes.

. However the stuff that's supposed to go in the XML is missing. Does anyone know what this attribute is?

<assets path="assets">

maybe?

That doesn't process them as binary though

<assets path="assets" type="binary">

perhaps?

thats interesting...

Is there anyway to disable graphical window on a Lime app?

To keep it as console-only?

why are you using lime in the first place if you just want the console?

Compiling

Okay sorry had to solve something and couldn't proper detail

it's probably possible to hide the graphical window, but it would still be created. I don't think there's a way to disable its creation entirely.

I'm using Lime as it is so far the only thing able to compile properly. Tried to setup hashlink but gcc doesn't seems to be a fan of it for some reason

you could try this:

haxe
package;

import lime.app.Application;
import lime.ui.WindowAttributes;
import lime.ui.Window;

class Main extends Application 
{
    public function new () {
        super ();
    }
    
    override public function createWindow(attributes:WindowAttributes):Window
    {
        trace("Hello World");
        return null;
    }
}

I currently have something like this, it's working

yet this is the output I'm having

For context my code(basically same as the one semmi sent)

hx
package;

import lime.ui.WindowAttributes;
import lime.app.Application;

class Main extends Application {
    public function new() {
        super();
        trace("Init");
    }

    public override function createWindow(attributes:WindowAttributes) {
        return null; //* Should never create window
    }
}

Had the "Attempt to create window!" trace on the createWindow function but removed it

My question is if it would be able to disable the SDL integration or if I'd be better of trying to figure out a way to make hashlink work

i recommend to use

tink_cli

and together with the poor haxe-parts of your application

(so that graphical and console-one is sharing the pure haxe-code)

do you just want to run something in headless mode?

Will give it a try, hopefully will work

Yeah, the idea is for this to be a TCP Server

ah okay, you don't really need lime then

just use standard cpp or hl

Deploy target will be a docker container(yet don't think it's that much of a required info)

you could even use node if you really wanted

My objective is to drive away from Node

The current code is running on pure Node.JS(typescript actually) but performance is starting to become a issue, even with optimizations