Re: Quarks: how to handle class file exclusion for non-qt & headless?

Hello all,

I just checked again and did not find anything in the help files:
do we have a list of directory exclusions per platform already?
Would be really useful for making quarks work everywhere
without requiring extra debugging/exclusions by hand.

I imagine it should be something like this:
Platform macOSwindowslinuxraspiraspiBBBBela  linux-vim, etc etc:
GUIheadl.
folder
osx+-------
win-+-----

linux--+++-+?+
GUI+++++-??-
scide_scqt++++--?-?-

thanks,
best adc

> On 05/04/2019, at 23:12 , [email protected] wrote:
>
> hi Alberto,
>
> On Fri, Apr 5, 2019, 4:58 AM <[email protected]> wrote:
>
>> Dear all,
>>
>> dear Brian & Wouter,
>> given the email exchange below, I hope you can help me:
>>
>> Is there a canonical way of putting GUI-related class files in Quarks in named dirs
>> so the quark works directly both in headless and ide/qt systems without extra steps?
>> If there is, it would be good to document it prominently :-)
>
> yes, i have been meaning to. it's complicated.
>
>> scide_scqt/     class files here are ignored on all non-ide, non-qt systems, yes?
>
> yes
>
>> GUI/                    does GUI/ also get ignored automatically on headless or non-qt systems?
>
> no
>
>> ???                     is there a separate special dir name for non-ide systems with qt?
>
>>
>
> yes, this is a command-line parameter to sclang.
>
>> I am asking because we currently have projects where the same setup
>> should run on multiple platforms, macOS, linux, windows (with IDE + qt)
>> and headless raspi and ideally also bela.
>>
>> The setup consists of some 8 quarks and a folder with .scd code files,
>> so I would prefer not to modify the quarks, but clean them up once,
>> so all GUI/IDE class files get ignored automagically.
>>
>> ( For the scd code files, we put all gui files in a separate folder,
>> and only load that if not headless: ~headless = \View.asClass.isNil; )
>
> the newest release has Platform.hasQt, would recommend using that if you're on 3.10.2.
>
> also, it is a priority for our next release (3.10.3) to offer the possibility of building sc without qwebengine.
>
> regards,
> brian
>
>> Thanks for any pointers,
>> best adc
>>
>>> On 16/09/2018, at 02:05 , [email protected] wrote:
>>>
>>> Hello Wouter,
>>>
>>> I believe the correct place to put them would be scide_scqt. This is not well-documented (there is a brief note in the Windows readme, but that's obviously not the right place for it).
>>>
>>> There is also a PR in the works to allow SC to be built without the webengine dependency.
>>>
>>> -Brian
>>>
>>> On Sat, Sep 15, 2018 at 4:23 AM <[email protected]> wrote:
>>> Hi list,
>>>
>>> I'm looking for a way to exclude my wslib and Unit Lib GUI classes when running a non-qt build of SuperCollider (cmake -DSC_QT=OFF) on Linux. I tried putting them in an scide_scapp folder, but that also blocks them out on builds with qt and IDE. I'm running the non-Qt build via vim on linux. (the reason for it to be non-Qt is because one single qt package - qt5-webengine-devel - was missing in the package list of this particular linux flavor). What would be the proper folder name to put them in?
>>>
>>> cheers & thanks,
>>> Wouter
>>> _______________________________________________
>>> sc-users mailing list
>>>
>>> info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
>>> archive: http://www.listarc.bham.ac.uk/marchives/sc-users/
>>> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/
>>
>> _______________________________________________
>> sc-dev mailing list
>>
>> info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
>> archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
>> search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/