> I said it to you elsewhere already: if you do nasty things (using the
> DESTDIR and expect that you can build against such "copied" (they are
> not *installed*, because DESTDIR != CMAKE_INSTALL_PREFIX) sources, then
> you are in it on your own. It doesn't mean the code base doesn't
> support
> Evolution depends on the evolution-data-server, not only as a usual
> library dependency, but also because things are just split into the two
> projects and to fix a problem in Evolution can mean to touch the
> evolution-data-server code, sometimes only there, sometimes on both places.
Thanks
> … Instead, use DESTDIR properly
I find that this happening here.
> (aka not at all,
I am using such an environment variable for intended purposes,
> because you are not a packager,
Such a view can be appropriate at the moment.
> and configure the project properly,
Such an expectation
> In file included from
> /home/elfring/Projekte/Gnome/Evolution/lokal/src/e-util/e-util.h:266,
> from
> /home/elfring/Projekte/Gnome/Evolution/lokal/src/e-util/test-proxy-preferences.c:18:
> /home/elfring/Projekte/Gnome/Evolution/lokal/src/e-util/e-webdav-browser.h:26:10:
>
> When you tell the software that the files will be located in /a/b (in
> this case by using -DCMAKE_INSTALL_PREFIX=/a/b) and then you install it
> into /g/h (by using DESTDIR=/g/h make install) then it does exactly
> what you told it.
This part should usually be fine.
> b) you do not need to
> I did not notice any limitation.
A build system configuration limitation was demonstrated by missing
a known header file which is available in another selected storage location.
>> I would like to reuse software components directly from a “staged”
>> (test) installation.
>
> Sure, then do
> https://www.gnu.org/prep/standards/html_node/DESTDIR.html
I have read the document section “7.2.4 DESTDIR: Support for Staged Installs”
once more.
> Hint: You misuse the DESTDIR variable.
I got obviously an other impression.
> Hence, there's nothing to be changed in the build process.
I
> could you use bug tracker to fill bugs, please?
I hope that the clarification will be continued with the bug report
“Make selection of installation contexts configurable for software build
components”.
https://gitlab.gnome.org/GNOME/evolution/-/issues/1226
Regards,
Markus
> and also always provided actual problem descriptions and use cases in
> your GitLab tickets (as requested many times before).
Do you find my experience report acceptable and reasonable for the desired
clarification of a compilation failure?
Regards,
Markus
> Not if you finally decided to follow the scheme and guidelines in
> https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
> (as requested many times before).
Would you get into the mood to achieve further improvements for the affected
software build system (eventually also
> could you use bug tracker to fill bugs, please?
I can register another clarification request also in an issue tracker.
> Apart of it being much easier to track the issues,
There can be a risk that the communication will evolve in ways
so that such an issue would be locked again before a
Hello,
I have installed a development version of the software “GNOME Evolution Data
Server”
into another test directory.
It seems that this directory selection deviates from assumptions or expectations
for commands which are mentioned in the document “Building Evolution from
sources”.
>> I imagined then that the module “alarm-notify” could be offered as
>> auxiliary for the service implementation.
>
> So it is, no?
I thought that circumstances would evolve in ways so that a repository like
“https://gitlab.gnome.org/GNOME/evolution-data-server/-/tree/master/src/modules”
would
> those are reasons, not opinions. They cannot be reconsidered. To be
> more specific, the module lives in Evolution, because:
> - it's Evolution's extension of the data server's code
I imagined then that the module “alarm-notify” could be offered as auxiliary
for the service implementation.
>>> There are reasons why it's where it is.
>>
>> Can they be reconsidered occasionally?
>
> Not if you don't explain which problem that would solve.
We came along clarification attempts if an installation dependency
is always appropriate for the system library directory.
> As a clear
>> Where do the recurring understanding difficulties come from?
>
> From your communication style and unwillingness to follow guidelines,
> as explained dozens of times before.
There are several factors involved which make also our
communication approaches challenging.
> Do you enjoy asking the
Hello,
A commit subject for a known software component contains the information
“Move evolution-alarm-notify to evolution-data-server”.
2018-05-11:
https://gitlab.gnome.org/GNOME/evolution/-/commit/499518d53c7e7c64bed3c58680edba49be477a4e
The component is still stored in a repository which
>> Should any failures for the loading and integration of desirable
>> modules/plugins
>> trigger corresponding clear warnings (or error messages)?
>
> Hi,
> you quoted the answer for this question in your own message. I miss a
> point of asking it, I'm sorry.
You might interpret an
>> But I do not see an error message which I would interpret as a direct
>> explanation for the missed display of the menu entry “Plugin Manager”.
>
> Aha, I see, Evolution doesn't know what modules/plugins should be
> loaded, thus it doesn't claim any error about them "missing". See above
> for
>> Would anybody like to take any other software design options into account?
>
> No.
Were I affected by another software evolution anyhow?
https://wpewebkit.org/release/wpebackend-fdo-1.8.0.html
https://github.com/Igalia/WPEBackend-fdo/issues
Regards,
Markus
>> home/elfring/Projekte/Bau/Evolution/3.36.5/Probe/bin/evolution:
>> symbol lookup error: /usr/lib64/libwebkit2gtk-4.0.so.37: undefined
>> symbol: wpe_fdo_initialize_shm
>
> Hi,
> I've not much idea on this one.
I got further software development ideas accordingly.
>
> to be honest, I did not notice any "program start parameters" you are
> mentioning now, to be in the original post of this thread.
The program was started without additional arguments from the test
installation directory while specific values were applied for
the environment variables “LANG”
> More importantly, you did not tell us *how* you build the Evolution.
> You use CMake, of course, but that's far from the answer for the *how*.
I find the applied command just ordinary.
elfring@Sonne:~/Projekte/Gnome/Evolution/lokal> cmake --build
~/Projekte/Bau/Evolution/3.36.5 -j 4
> to be honest, I did not notice any "program start parameters" you are
> mentioning now, to be in the original post of this thread.
See also:
https://mail.gnome.org/archives/evolution-hackers/2020-November/msg0.html
Repetition:
elfring@Sonne:~/Projekte/Bau/Evolution/3.36.5/Probe> LANG=C
>> * Do you care for questionable software behaviour according to customised
>> run time environments?
>
> The original author usually avoids bringing up specific topics and
> instead posts vague unclear questions which waste other people's time.
What is unclear about a check approach for the
>>> against system evolution-data-server (eds) and you do not like
>>> that Evolution installs its eds module into the directory,
>>> where eds expects to have the modules installed.
>>
>> I suggest to recheck the functionality from the CMake scripts.
>>
>> elfring@Sonne:~> /usr/bin/pkgconf
> To get some background information to the archive readers (which I
> learnt from the GNOME's GitLab ticket(s) you filled): you've been
> building only Evolution
I built a selected version of this program.
> (thus not following the Building wiki page from its top)
This kind of response will
>> I am looking for better support of advanced software build techniques
>> so that more tasks can eventually be automated in helpful ways.
>
> Wanting advanced techniques means being an advanced person,
I suggest to adjust possible target conflicts.
> which is against being nice to newcomers,
>> Do you use a command like “DESTDIR=Test cmake --install
>> build_directory” for this purpose?
>
> Hi,
> I use what is written on the wiki page. I guess I mentioned that in my
> previous mail.
>
> If you do not want to follow that wiki, then, I believe, it doesn't
> make sense to request
>> Would you like to continue the clarification for the topic
>> “Improve descriptions for software build dependencies”?
>> https://gitlab.gnome.org/GNOME/evolution/-/issues/1198
>
> Hi,
> it's a Wiki page. Basically anyone can improve it. It's definitely not
> improved by opening bug
> you may want to consult:
> https://wiki.gnome.org/Apps/Evolution/Building
I read this document already.
Would you like to continue the clarification for the topic
“Improve descriptions for software build dependencies”?
https://gitlab.gnome.org/GNOME/evolution/-/issues/1198
Do you try the
Hello,
I have installed the software “GNOME Evolution 3.36.5” into another test
directory.
I can start the application like the following on my Linux system.
elfring@Sonne:~/Projekte/Bau/Evolution/3.36.5/Probe> LANG=C
32 matches
Mail list logo
