Introduction 2.1. TDE is the Trinity Desktop Environment. The project was initiated by Matthias Ettrich in 1996 and originally called the K Desktop Environment. The aim of the TDE project is to connect the power of the Unix-like operating systems with the comfort of a modern user interface. For additional information about TDE, check the Trinity web site at 2.2.

On which platforms can I expect TDE to work? TDE is a Desktop Environment for all flavors of Unix-like systems. While most TDE developers use Linux based systems, TDE should run on a wide range of systems.

You might need to tweak the source code a bit to get TDE to compile on different variant of Unix-like systems, or when not using the GNU development tools, in particular the gcc compiler. Why should I use TDE? TDE provides a traditional computer desktop that is snappy and responsive. A project goal is to provide a highly customizable desktop without forcing any particular feature or effect on users. TDE comes with many software tools to provide a productive and enjoyable computer desktop system. Is TDE a window manager?

No, TDE is not a window manager. While TDE includes a sophisticated window manager (TWin), TDE is much more, providing a full integrated desktop environment. TDE includes a web browser, a file manager, a window manager, a help system, a configuration system, many tools and utilities, and many applications, including but not limited to mail and news clients, drawing programs, a PDF and a DVI viewer and so forth. Is TDE a CDE, Windows or Mac OS clone? TDE is not a clone. Specifically TDE is not a Common Desktop Environment (CDE) or Windows clone. While developers have and will continue to glean the best features from existing desktop environments, TDE is a unique environment that has and will continue to go its own way.

On what platform is TDE based? TDE uses C and the. The TDE development team now maintains the Qt3 toolkit, renamed TQt3. Is TDE free software?

Yes, TDE is free software according to the GNU General Public License. All TDE libraries are available under the LGPL making commercial software development for the TDE desktop possible, but all TDE applications are licensed under the GPL. TDE uses the, which, since version 2.2, is released under the GPL. Both TDE and Qt can be made available on CD-ROM free of charge. No runtime fees of any kind are incurred.

Why the rebranding and renaming efforts? Why not continue calling the software KDE?

The 'KDE' name, various logos, and related efforts are trademarked by the KDE Foundation. Since the Trinity project is not affiliated with the KDE Foundation, legally we can't use their trademarks. Why the change in version numbers? Trinity evolved from the last KDE 3.5 release, 3.5.10.

Subsequent Trinity releases followed that numbering scheme. Release R14.0.0 marks a turning point in Trinity history because a great deal of the code infrastructure was changed. While those changes do not effect the usability or look-and-feel of the desktop that users enjoy, Trinity developers believe a change in the version scheme distinguishes when those changes occurred. An original project goal by users was to retain the flavor of the original KDE 3.5 desktop. That goal remains intact.

To reflect that original goal, the last number in the original version scheme is retained in the new version scheme but is now the primary version number. While the infrastructure has changed, the desktop itself remains the same as the original KDE 3.5. This new version scheme indicates a modest divergence from the original KDE 3.5 series and that Trinity is now its own desktop environment. The new version scheme reminds users that Trinity retains the original KDE 3.5 design, but is moving forward as a separate desktop project. How is Trinity different from KDE4? Both desktop environments share common roots to KDE 3.5.10, which was the last official release of KDE in the 3.x series. Many KDE developers wanted to break from that code chain and tool sets to start afresh.

Thus was born KDE4. In addition to moving to the Qt4 tool set, the KDE developers revamped the underlying KDE code set. KDE4 and Trinity have different philosophies about work flow preferences.

KDE4 developers want to support certain work flow concepts and techniques. Trinity developers want to maintain a 'traditional' desktop environment. For example, KDE4 offers the following tools:. Semantic desktop through Nepomuk.

Compile Trinity For Mac

PIM (Personal Information Management) data caching through Akonadi. Desktop file searching through Strigi. Activities, a computer desktop metaphor for managing tasks and activities Whereas TDE offers the following:. Desktop search through the locate:/ tdeio-slave and Beagle.

Integrated PIM suite with plugins. Related task management using multiple desktops The KDE developers support alternate desktop interfaces, such as those used with netbooks, tablets, and smart phones. TDE provides a single interface that is optimized for the mouse/keyboard HCI (Human-computer interaction) model. Both desktop environments provide an excellent choice for various work flows but differ in approach. Trinity leans toward user expectations of how desktop environments have functioned traditionally. There is a sense of familiarity with that environment many people like.

Similarly other users prefer the work flow features offered by KDE4 because those features match their expectations of how they want their computer to behave. The difference between the two environments does not mean one is better, buggier, or slower — only that they are different and appeal to different types of people. Although sharing a common heritage, both desktops appeal to different groups of people. As always with free/libre software, there is a choice. About this FAQ Getting TDE © 2011-2018 Trinity Desktop Project.

There appears to be that have been written to help get you set up cross compiling for the Mac; I can't say how good they are, or how applicable to your project. In the documentation, they refer to for cross-compiling for 10.4, and for cross compiling for 10.5; those instructions may be more helpful than the script, depending on how well the script fits your needs. If your program is free or open source software, then you may wish instead to create a portfile (documentation ), and allow your users to build your program using MacPorts; that is generally the preferred way to install portable free or open source software on Mac OS X. MacPorts has been known to run on Linux in the past, so it may be possible to develop and test your Portfile on Linux (though it will obviously need to be tested on a Mac). Get '. Get '. Compile/Debug/Integrate-and-test your code on the new OS to make sure everything works When you are trying to get something working on multiple platforms you absolutely must compile/run/integrate/test on the intended platform.

You can not just compile/run on one platform and then say 'oh it should work the same on the other platform'. Even with the a really good cross-platform language like Java you will run into problems where it won't work exactly the same on the other platform. The only way I have found that respects my time/productivity/ability-to-rapidly iterate on multiple platforms is to use a VM of the other platforms. There are other solutions like dual-boot and ones that I haven't mentioned but I find that they don't respect my productivity/time. Take dual-booting as an example:.

I make a change on OS 1. reboot into OS 2. forget something on OS 1.

Free MKV Converter is easy to use. And it does not contain spyware or adware. Shining mxf converter 6.6.6 free download for mac.

reboot into OS 1. make a change on OS 1.

Compile Trinity For Mac Free

reboot into OS 2. BAM there goes 30 minutes of my time and I haven't done anything productive. Apple development is a strange beast unto itself.

OS X uses a port of GCC with some modifications to make it 'appley'. In theory, it's possible to the the sources to the Apple GCC and toolchain as well as the Apple kernel and library headers and build a cross compiler on your Windows machine.

Why you'd want to go down this path is beyond me. You can have a cheap Mac mini from $600. The time you invest getting a cross compiler working right (particularly with a Windows host for Unix tools) will probably cost more than the $600 anyway.

Compile Trinity For Mac Pro

If you're really keen to make your app cross platform look into Qt, wxWidgets or FLTK. All provide cross-platform support with minimal changes to the base code. At least that way all you need to do is find a Mac to compile your app on, and that's not too hard to do if you have some technically minded friends who don't mind giving you SSH access to their Mac. The short answer is kind of. You will need to use a cross-platform library like. There are IDE's like QT Creator that will let you develop on one OS and generate Makefiles for others.

For more information on cross platform development, check out the cross-platform episodes of (note that the series isn't over and new episodes appear to come out weekly). As other answers explain you can probably compile for a Mac on Windows or Linux but you won't be able to test your applications so you should probably spend the $600 for a Mac if you’re doing professional programming, or if you’re working on open-source software find a developer with a Mac who will help you.