Hi Reape10, it's definitely a long list.
At the moment we're concentrating on fixing regressions to get the next release
out.
After that is a good time to tackle new features, especially if people help us
with code contributions.
--
You are receiving this because you are subscribed to this th
Closed #36.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/36#event-1746369257___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Thanks for the report, this is fixed now.
The remote reference GC has now been configured to only kick in every couple
seconds, and the GC statistics are hidden behind a debug condition. I.e. to now
reproduce such volume of debug spew, you have to run beast like this:
BSE_CONFIG=gc-seconds=1 BSE
Hi Mike, I don't see anything like that with g++-7.2.0 and not in our travis
builds either:
https://travis-ci.org/tim-janik/beast
Is this with current git master?
And do you see the same when using an older gcc?
--
You are receiving this because you are subscribed to this thread.
Reply to this
HI, I guess the Beast sources are not yet equipped for /usr/bin/python pointing
to a python3 executable instead of python2. I'm looking into that now.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-ja
Thanks, merged, plus I re-added your comments.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/42#issuecomment-407911435___
beast mailing lis
Closed #42.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/42#event-1753713490___
beast mailing list
beast@gnome.org
https://mail.gnome.org/
There must be something else going on with your build. Python-2.7 and gcc-7
definitely works for current master, see e.g. here:
https://travis-ci.org/tim-janik/beast/jobs/408290581
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Can you provide a link to the source code for this plugin?
It seems to be a Ladspa plugin by David (he's contributed to beast before). If
that's Ladspa v1, Beast supports it already.
Support for Ladspa V2 in Beast is on the todo list of @swesterfeld.
--
You are receiving this because you are sub
Closed #35.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/35#event-1766533225___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Trackview scopes and mixer meter levels are fixed as of commit
db4332b3503c3a618052fe0a8bbde7504e724570.
FFT scopes should be reimplemented using a new (and useful) visualisation style.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it o
Closed #48.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/48#event-1771081618___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Hey @Reaper10.
Most DAW features are on our long-term todo list, full automation support and
MIDI recording is definitely on it. I've just released 0.12.0-beta.1 which
ships the start of a new UI that's much closer modeled to match well known DAWs.
Note that for general questions and discussion
Closed #45.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/45#event-1771265415___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Hi Milk, please give the 0.12.0-beta.1 tag or the 0.12.0-beta.1-tarball a try
and come back if you still run into bugs in the Beast build. Rapicorn is *not*
needed for 0.12.0-beta.1.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
Closed #43.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/43#event-1771266038___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Please give the 0.12.0-beta.1 tag or the 0.12.0-beta.1-tarball a try and come
back if you still run into bugs in the Beast build. Note that Rapicorn is not
needed for 0.12.0-beta.1.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on G
The splitting definitely makes sense.
Feel free to close this bug when you're done filing individual requests (or
I'll do it after some grace period).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-ja
Closed #57 via cf7c2bc0b42405d72aca62d69b757535a929111f.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/57#event-1774064729___
beast mailing
Closed #33 via 6a89141824996514eee439b124d7f38f5be5f97d.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/33#event-1774119201___
beast mailing
This bug tracker is about Beast - the Linux Music Synthesizer and Composer
software application.
It is not related to a particular car video system.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-jani
Closed #61.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/61#event-1783901452___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Closed #62 via b1796370eea3cf35e9b56a9491be5cba41429882.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/62#event-1793468938___
beast maili
Closed #38 via c96f967084892c32103e96d1fe9330457656e64e.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/38#event-1796578879___
beast maili
Hi, it's not exactly that your version is too new.
This is my system:
$ xmllint --version
xmllint: using libxml version 20904
And Beast checks for 20901.
The problem is in the path you're using, out comparison macro picks up the
"version" digits from the absolute pathname of your xmllint, and t
Closed #63 via 8674c397419858b37d30ee704cfe641e507d10da.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/63#event-1803484382___
beast maili
Hi Stefan, looks interesting.
I think I would have kept using iview->container plus a few more casts instead
of introducing BstTrackView.song, to ensure that iview->container and
BstTrackView.song cannot get out of sync.
Your approach might be more convenient and I guess the
bst_item_view_set_c
Merged #64 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/64#event-1805221122___
beast mailing list
beast@gnome.org
https://mai
I see a couple issues on your system before compilation even starts. Here're
some questions about your setup:
- what kind of system are you building on, why are many tools under /nix/ ?
- why don't you have pwd or file?
./configure: line 3641: /bin/pwd: No such file or directory
./configure: lin
Hi Magnetophon.
I've read up a bit about NixOs. Because it installs everything in their own
paths, hardcoded paths in other packages won't work well there. I'm happy to
fix that in Beast, but it sounds like there's a fair bit of work involved. So I
suggest we change our work setup for that. I re
You seem to be asking for an "internal" wave viewer, so it sounds like you
haven't tried out the built-in multi-sample wave viewer in Beast yet. It's
right there behind the "Load" and "Editor" buttons you can see at Beast startup.
--
You are receiving this because you are subscribed to this thr
Closed #46.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/46#event-1809179592___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Closed #50.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/50#event-1809182755___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Part of what you're asking for here is already implemented in Beast - e.g. we
have a wave oscillator that can remix and playback samples at different notes /
mixing frequencies with appropriate an anti-aliasing filter. Or, we have
Soundfont 2 support already, courtesy to @swesterfeld's efforts.
Closed #51.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/51#event-1809183913___
beast mailing list
beast@gnome.org
https://mail.gnome.or
In issue #44, @swesterfeld has already confirmed out plans to port Beast to
Windows at some future point. There're no concrete plans for Mac atm, and no
one volounteered to attempt a port yet.
There hasn't been any progress on this issue for more than two weeks, and
it's not helpful to let th
Closed #52.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/52#event-1809187070___
beast mailing list
beast@gnome.org
https://mail.gnome.or
This issue as currently formulated is very broad, e.g. definitely not useful to
track @swesterfeld's VST-2 development intentions. And I trust that he'll be
able to file his own PR if he has something that's useful to start a merge
discussion on VST-2. Other than that, there hasn't been any inpu
Closed #67.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/67#event-1809189303___
beast mailing list
beast@gnome.org
https://mail.gnome.or
In the Beast Gtk+ mixer UI of which you've attached a screenshot, the volume
for the left and right channels can be adjusted in sync or individually,
toggled by [S]. In the new electronjs UI that's being developed, panning may
become a function of a knob in the track controls.
If you can get Be
Thanks for the PR, a couple comments:
> + SfiInt lleft = self->song.loop_left();
Use just int, float, etc in new code, instead of gint or SfiInt.
> + BseSong *self = const_cast (this)->as();
This should be "as", without the extra space.
> + bool loop_enabled = self->loop_enabled_SL;
Yo
Closed #65 via 626efb2af3e78490c23278c435f6c159e7aeed1b.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/65#event-1809442347___
beast mailing
tim-janik requested changes on this pull request.
I've added some review comments inline (trying this out in github to see if
that's a helpful feature). The most important point is the fact that as<> (or a
new bse_cast<>) will be temporary measures that we ultimately want to get rid
of in libbs
tim-janik commented on this pull request.
Thanks a lot, minor comments inline.
> +
+void
+SongImpl::tick_pointer (int tick)
+{
+ BseSong *self = as();
+
+ if (uint (tick) != self->tick_SL)
+{
+ // this property has no undo
+
+ BSE_SEQUENCER_LOCK ();
+ self->tick_SL = tick;
+
Merged #68 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/68#event-1812662311___
beast mailing list
beast@gnome.org
https://mai
Merged #71 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/71#event-1819383340___
beast mailing list
beast@gnome.org
https://mai
Good catch, thanks for taking the time to fix the README.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/71#issuecomment-417488381___
beast
Thanks a lot Stefan.
I'm not sure that "TPQN" is any better than "Ticks" for users at the UI, at
least I'm not aware of another sequencer that has TPQN labels... I think in
either case users will need the tooltip to decipher what the property is about.
There's one other thing I noticed during re
Closed #69 via dc84f2c563775472ac985cf8bdad40c75423e49d.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/69#event-1819415121___
beast mailing
Hm, I'm not seeing that with g++-5 or g++-7.3.0. Also not with clang++-4, 5 or
6 (clang requires recent master though).
I'll see if I can get my hands on g++-8 in the next couple days...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
@magnetophon, I'm not sure how exactly I can be of further help here.
>From what I understand, NixOS requires a lot of file path patching, from the
>output of configure, to paths hardcoded in Makefiles, and paths in scripts.
At the very least, you'll need /usr/bin/env.
I'll happily take patches
Closed #56.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/56#event-1819475009___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Please not that LADSPA v1 plugins are already supported, that includes cmt
plugins released with a LADSPAv1 API. LADSPAv2 support is also planned, which
could bring even more supported plugins.
Since there's no immediate action required on this bug and it's been sitting
here for over 3 weeks, I'
I managed to reproduce this here, using:
LANGUAGE= LANG=de_DE.UTF-8 beast
The duplicate entries are due to a mixture of translated labels used in the
menu paths. I.e. in one place we create a menu item "_Audio Quellen" from
"/_Audio Sources/", in another place we refer to that menu entry as
Hey Stefan,
since you're brain storming here and started a discussion, I'm taking this to
the list and off the bug tracker.
There are a few reasons I have not attempted to add enforcement with the new IDL
API.
First, the range information the IDL layer has is informal and mostly passed
from *.id
Closed #74.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/74#event-1821554347___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Great input Stefan.
But please take brainstorming and discussions to the mailing list:
https://mail.gnome.org/archives/beast/2018-August/msg00101.html
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-j
Thanks for the suggestions. Making slag a part of beast would be more than a
little work though, beast already had pattern sequencing more than a decade
ago, and is not based on Qt 3.
But I'll try to keep your ideas in mind, when I get around to hacking on
sequencing / drums again.
--
You are
Closed #77 via 9bdf9e824c5dae4d4a3eccf03b77e423c93e25ae.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/77#event-1834401243___
beast mailing
Thanks a lot Stefan, good catch!
I'd be happy if you reviewed my other changes as well, i.e. what the diffs
between branch merges give you:
git log -p --first-parent
You'd have to skip the odd po/* diff though, not sure if git log can filter
that.
--
You are receiving this because you are s
Thanks Stefan, great to see steady progress here.
But note that travis-ci shows, that your changes broke the syndrum audio test
in all build variants, please take a look at that.
About volume clamping, taking a look at other DAWs suggests that this should be
done at the UI and doesn't need to b
> > On 09.09.2018 15:21, Stefan Westerfeld via beast wrote:
> Instead of two volume sliders we only need one. The two meters could be put
> next to each other. So this would mean left-to-right volume slider (only one
> slider), scale numbers (-96..+12), left meter, right meter.
Do you intend to
> So it looks like the first device that works for beast in the list is `PCM
> "front:CARD=Loopback,DEV=0"`. Right?
Yes, that's right. I'm astonished you got a DEVICES_MISMATCH for the other
devices though. That error is only triggered if the sampling frequency
mismatches, the period size or co
On 14.09.2018 15:28, Stefan Westerfeld wrote:
>> I hear what you mainly want to simplify though, and I think a good chunk of
>> that can be achieved with convenience macros, even if that's less elegant to
>> the trained C++ eye.
>> Assuming we move properties in to the *Impl classes and out of the
Hey Stefan, thanks for looking into this.
I don't fully follow the argument you make in your comment though.
* Why should an undo step be recorded for restoring a connection that doesn't
exist in the first place?
* Also, with your code, calling disconnect_bus() repeatedly will record more
and mo
Closed #81 via 408c09eff7ff8859268dd957c7baa219282076c7.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/81#event-1870620074___
beast mailing
I've rebased and squashed the PR and then fixed a couple build issues so it
actually compiles and works for me (btw namespaces must be labeled with
comments in Beast, I had a hard time figuring the beginnins and ends of the
anon namespaces). The howto should mention that users also need to insta
> Unfortunately, I'm having the same problem on GNU Guix (also a functional
> package management system like Nix).
Hey @rekado, please create a new issue for this, so it's a) about GUIX, and b)
we're discussing stuff on an *open* issue ;-)
If possible, it could help if you join #beast on irc.gim
Merging of the Soundfont branch introduced a global (per project) mutex around
fluidsynth in bsesoundfontrepo.cc that prevents parallel processing of engine
modules.
E.g. for a polyphonic track, thread 1 might be processing a fluid voice, while
threads 2,3,4 try to process polyphonic voices of t
Closed #87 via fd654d63eb55288b3f2e99ee60fb652df5fbeb51.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/87#event-1921780454___
beast mailing
I managed to reproduce this with g++ (GCC) 8.1.1 20180712 from Fedora-28.
But it looks like a gcc SFINAE bug to me, it treats a substitution failure as
error, even though an alternative substitution exists. All clang versions and
gcc <= 8 compile this correctly.
it's not too easy to isolate th
Managed to isolate a test case, g++ bug report can be found here:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87748
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/72#issuecomment-43
There's no easy workaround for the g++-8.2 SFINAE bug, the code portion that
triggers this is vital for the function calls between the UI and the sound
engine. So, unless g++-8.3 fixes this and Fedora-28 decides to upgrade and
ship, g++-8.3, Fedora-28 builds can unfortunately not be supported.
Closed #72.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/72#event-1926780378___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Closed #53.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/53#event-1926799297___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Thank you for your input.
Unfortunately there hasn't been any progress on this issue for several weeks,
and it's not helpful to let this issue stay open with just a vague feature
description.
So it is now closed to avoid it cluttering our list of bugs that actually are
being worked on.
--
You
Thank you for your input.
Unfortunately there hasn't been any progress on this issue for several weeks,
and it's not helpful to let this issue stay open without anyone volunteering to
actively work on an implementation.
So it is now closed to avoid it cluttering our list of bugs that actually are
Thank you for your input.
Unfortunately there hasn't been any progress on this issue for several weeks,
and it's not helpful to let this issue stay open without anyone volunteering to
actively work on an implementation.
So it is now closed to avoid it cluttering our list of bugs that actually are
Closed #55.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/55#event-1926802618___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Closed #54.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/54#event-1926801800___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Thank you for your input.
Unfortunately there hasn't been any progress on this issue for several weeks,
and it's not helpful to let this issue stay open without anyone volunteering to
actively work on an implementation.
As stated previously, new ideas are best discussed on the mailing list, and
Closed #59.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/59#event-1926804846___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Closed #60.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/60#event-1926807012___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Thank you for your input.
Note, we've already had portaudio support in the past. That was discontinued
due to limited interest on Linux.
Unfortunately there hasn't been any progress on this issue for several weeks,
and it's not helpful to let this issue stay open without anyone volunteering to
Thank you for your input.
Unfortunately there hasn't been any progress on this issue for several weeks,
and it's not helpful to let this issue stay open without anyone volunteering to
actively work on an implementation.
So it is now closed to avoid it cluttering our list of bugs that actually are
Closed #47.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/47#event-1926812776___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Closed #73.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/73#event-1926814865___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Thank you for your input.
Unfortunately there hasn't been any progress on this issue for several weeks,
and it's not helpful to let this issue stay open without anyone volunteering to
actively work on an implementation.
So it is now closed to avoid it cluttering our list of bugs that actually are
Beast dosn't currently provide an Arpeggiator module.
@swesterfeld may or may not have input on implementing one.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/75#issuecomment-43312
Closed #75.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/75#event-1926818651___
beast mailing list
beast@gnome.org
https://mail.gnome.or
> For the sake of this discussion, we only need to do three things:
[...snip...] removing lots of *symptom* investigation [...snip...]
You never get to the root cause here, which is removal of connections without
undo recording in the first place.
> which we can summarize as the input/outputs o
Closed #89.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/89#event-1980562870___
beast mailing list
beast@gnome.org
https://mail.gnome.or
If you're building 'master', take a look at .travis.yml.
applyenv.sh Has been superceeded since we're supporting Fedora builds.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/89#issu
> Thanks for making an AppImage. However, it was compiled on a "too new" system
> so that it won't run on Ubuntu 14.04, which is still a supported distribution
> at this point
I'm fully aware of the AppImage Hub requirements regarding old distributions.
However there is no way that our code bas
You can pick a release tarball from here:
https://beast.testbit.org/#downloads
The tarballs have a configure script.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/91#issuecomment-4
Closed #91.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/issues/91#event-2144646526___
beast mailing list
beast@gnome.org
https://mail.gnome.or
Beast supports ALSA out of the box. A Jack driver is in development.
If the mixer is moving, that means it's actually playing back using some kind
of ALSA device.
You might have a soundcard with multiple outputs, or have mixer settings that
mute the PCM channel that Beast uses for playback though
Beast supports ALSA out of the box. A Jack driver is in development.
If the mixer is moving, that means it's actually playing back using some kind
of ALSA device.
You might have a soundcard with multiple outputs, or have mixer settings that
mute the PCM channel that Beast uses for playback though
Support and depend on C++17.
Our current base platform, Ubuntu-18.04 ships with clang++-6.0 and g++-7.3,
both of which have support for -std=gnu++17.
Moving to C++17 can help with cross-platform filesystem access, it has lambda
simplifications and most importantly std::variant.
--
You are recei
Atm, we still build with and depend on aidacc and sfidl.
Use of sfidl should be finally phased out, aidacc should be simplified to just
help with:
* interfaces, methods, enums, property accessors.
* meta data on properties and enum values.
* event delivery.
* support for an Any/Variant type for dy
1 - 100 of 267 matches
Mail list logo
