nsITobin don't think so. Tools should have the same layout. Just a different base.

it chilly this morning

Good morning #SeaMonkey

nsITobin greetings

nsITobin just did a 2.53 build with only build tools vs2022 and the 141, 142 and 143 toolsets installed so should be fine for 2019 too.

Tools seem to have much less bloat indeed. Needed only to remove vctip.exe

I will give it a try with the vs2019's vs2019 build tools as currently configured .. while there may not be an issue.. i remember it was hell trying to use 2015 build tools on 2017 AND keep normal 2015 working when I tried to solve it for UXP based on your attempt.. I just wanted it all.. as typical :P

tossing a coin if I should fix 2.49 for the 141 toolset

VS2017 can no longer compile 2.53 so removed from it.

what would 2.49 offer that seamonkey on uxp wouldn'

aside from XP compat

frg: are you still releasing updates for 2.49?

security ones

nope. Would just be for the xp fans to self compile.

well if one wants to give seamonkey 2.49 as a special gift to xp users I think one should do a special final release short of actually compiling it with special branding already in place so they don't have to do anything cause that has been a trouble point in the past.. make a big deal about it.. and then see what happens

Not sure if I want to spend time for doing a release. Would only do it so that I have the option in my build setup and less build envs. So mostly selfish me.

yeah pain alreayd trying to balance these envs and keep them clean and free of mangling

i have to work extra hard to have multiple build eras working on one machine but it comes at the cost of being way easier to bust

but i get efficiency

Have 3.4 and 4.1 separate thanks to the state path now set in start-shell.bat: SET MOZBUILD_STATE_PATH=d:\mozilla-build\workspace34

Works for 3.2 too so they can all co exist.

2.49 would be riding mb 2.x right?

Nope 3.2

nsITobin wondered if /build/windows_toolchain.py was used. Now I know. Not :)

so out the door with a bunch of hardcoded msvc references.

doesn't that bust start_shell_vs* files hacked to continue providing the vars to the build system?

19 The ``build/windows_toolchain.py`` script is used to build and manage

20 Windows toolchain archives containing Visual Studio executables, SDKs,

21 etc.

no all in build/moz.configure/toolchain.configure and friends.

See Bug 1289641

OH that's part of bootstrap

or .. was

lol

or would have been

depends on your perspective

either way automated mozinfra

gitlab 2.53 updated for it

nsITobin rust compiles in central are still great.... ibb.co/fVZb0xp9

10 forking GB

version?

cause 1.82 is behaving memory wise

for j6

but then again linking libxul has taken that much ram before on windows

-j8 with latest 1.85

libxul could have linked in shared xpcom dlls instead of rolled in and NONE of this would have ever been a damned issue

for fifteen bloody years now

It is no longer 2010 so I can live with 8 GB for all but not 10GB plus compiles plus something

fits into a 16gb windows vm i am fine.. beyond that i am screwed

Hey now its 18GB for rust. Have assigned 24GB to the vm.

19 and 98% mem usage

nsITobin STATUS_STACK_BUFFER_OVERRUN and needs more ram.

Totally whacko

yep

I need to look into rust, because now I'm wondering how come it can get so high memory consumption

is it doing links in parallel or something?

njsg: they fucked it up cause 1.82 works fine

its always gonna be high memory consumption but this is ridiculous

I can go back to 1.82 but not sure it would help. j8 and normal optimize might be it.

Needs more electrolytes!

1.83 MAY be fine too but 4+ seems to have an "issue"

gonna try .. know in 70 minutes

I think everyone should take advantage of these cpp apps going rust to learn rust so it can be translated back to plain C

and of course the web gonna be the web and there's people saying this is okay because unused ram is wasted

solve two issues at the same time

lol

look, there are good ways to use RAM, this almost surely isn't one of them :-P

njsg: the world wide web or the walled garden corperate mandated open web

cause there is a difference in my book

living standards are not formal standards they are endrun mandates by socially and economically more powerful groups

unused ram is wasted?

I'm sorry.. I thought this computer was a multiprocessing system.. I do have other shit to do while I am waiting for 70 minutes for mozilla to compile :P

apparently the only place where the usage of ram isn't advocated in this way is several Microsoft operating systems

that is kinda tough when all my ram is being used for one series of operations

having such behaviour in applications and utilities seems to go counter the idea of a system where, yes, you do other stuff

well windows historically without memory protection and shit has to ensure it has enough for its self and later MUST ensure it has enough for its self so it can mediate everything

now its just.. wasted cpu time and electricity

cause efficiency doesn't matter

I miss the "you own the world" memory model of Windows 9x :D

now you can't even really own your own files on a cellphone

does destiny.manifest ring any bells?

Meeting time in 27 minutes - wiki.mozilla.org/SeaMonkey/StatusMeetings/2025-03-09

today?

k

nsITobin yes as in 18 minutes

IanN_Away: sent you CCI details :)

Meeting time - wiki.mozilla.org/SeaMonkey/StatusMeetings/2025-03-09

hi .*

hi njsg

greetings

are we expecting rsx11m?

or has rsx11m succumed to DST?

either way...

Who's taking minutes?

I think he wanted to attend

me

thanks

summer time might have derailed him :)

Nominees for Friends of the Fish Tank?

welcome rsx11m

IanN for still trying to make cZ a better place.

Hi rsx11m

Sorry, a bit late today...

rsx11m: hi

Hi *

seconded

rsx11m: blame DST

always ;-)

failing that POTUS

Action Items

bau

Status of the SeaMonkey Infrastructure

ewong is still on the configs and has set up some tasks on the Windows builder.

Old Linux and Windows builder are gone.

or should be very very soon

yeah. ewong is also looking at signing

Status of the SeaMonkey Source Tree

nsITobin and I made central complie again. Mostly him.

^compile

central patch queue updated for it.

For 2.53 I removed VS2017 support becuase the compiler can no longer be used. We need later c++ features. Added support for VS2022 but only for the VS2019 toolset currently.

SO VS2019 and Vs2022 can be used also the build tools.

rust 1.83 for central seems largely ram behaved as well

1.84/85 seem to have memory leak issues

(is it memory leak or just increased usage? any visible difference in compile times or CPU usage?)

something to research njsg

where are we on rust for 253? cause I still been using 1.73

1.73 forever for now

wasn't there an upper limit to allow NT 6.1?

yes and macOS 10.11

so this ram thing may not go away

If we set macOS 10.12 as minimum I need to check but it is either 1.75 or 1.76 then.

1.73 seems stable for now.

Release Train

still no eta for 2.53.21 I didn't do much soruce wise for the last 3 weeks but didn't notice any urgent fix needed either.

Release Train

already there :)

Skip Betas yet?

Extensions Tracking

nsITobin not planned

bau. I still need to look into the add-on sdk but no time.

is the add-ons sdk worth keeping?

beyond devtools?

There was one add-on which was still being updated but we broke it.

"Drak Backgorund and Light text"

^Dark

Not happy about it but complaints are few.

Still would like to fix it.

is that the one?

yes

jetpack extension

well that answers my question

I presume it is github.com/m-khvoinitsky/dark-backg…d-light-text-extension/tree/jetpack

that matches xpi contents

IanN:

yes but the webext version in master

so fix jetpack version or work out what's needed to get webext version working

did it ever have a normal extension form?

IanN: betting on webextensions on this codebase ever working without modifications to the extensions them selves simply wasn't possible 10 versions ahead certainly not 75

webext is crap and needs soo much work. And with manifest v3 it gets crappier.

beyond content blockers and site specific moding extensions.. what is the appeal of webextensions.. they can't DO much more than that or what some webapi says

but you'll be able to do nothing, across "all" browsers!

but this is an agrument that can go on for years.. and has.. soo enough out of me on it for now ;)

It is mostly lego and the real support is in the browser but this is something we can debate for years so i won't start it :)

duplos maybe

2.Next, Feature List, Planning and Roundtable

yeah with v3 it is Duplo. With v4 it will probabably be prefabricated :)

bau. Real life took over lately and I wasn't much in the modd for more but need to work on wip. Another site I use frequently broke because of js.

would a site to report broken sites be useful to us with some annotations?

have checkboxes users can check for which clients they tried

etc

depends if it will capture new, useful information

and of the SNR

nsITobin I can file breakage all day. We just need to fix some of it so I would say now. 90% es class fields, dynamic imports, BigInt and the css

perhaps it'd be better to round up suggestions of things to check first in a tutorial-ish text, unless there's already such a page somewhere

I'll let it simmer in mah brain for a while

thanks

AOB