Over the years, we’ve received some feedback from IT pros who weren’t thrilled with the fact that RDM didn’t always play well with Microsoft ActiveX. Some of the main headaches included:
- When logging off or disconnecting from a client server, the RDM window would hang and have to be shut down.
- If an open VPN session ended and users weren’t present (i.e. if they had stepped away from their computer or device), RDM would hang and crash.
- Sometimes, when using ActiveX, RDM would crash for no apparent reason.
You’ll hopefully note, however, that I used the word “included” up there instead of “includes”, because I have some wonderful pain-relieving news: FreeRDP is now integrated in RDM as an alternative to ActiveX!
![Mac Mac](/uploads/1/1/7/8/117843333/469160796.jpg)
- Go to File – Options – RDP
- Switch your default RDP type from ActiveX to RDP (FreeRDP).
Opening Darwin was not simple. Apple’s development work on Mac OS X is managed using XBS, a complex and publicly undocumented internal build system; since nobody outside of Apple has access to the system, it was very difficult to build functional installs of Darwin from the source code as changes were introduced. I'm running Mac OS X 10.6.6. I have some data-only RPMs that I'd like to build. Until recently I've done most of my development on a VM running CentOS, but one by one I've been able to transition these tasks to the Mac proper.
What if you want to apply the change to specific RDP sessions instead of all of them? No problem:
- Choose a session to edit.
- Select the General side menu and then click on the Advanced
In the RDP Version dropdown menu, select RDP (FreeRDP). (Note that if you select Default, RDM will automatically use the option set under File – Option – RDP.)
There might still be some limitations as what FreeRDP can do, but please don’t be shy, tell us and we will try to fix it as soon as possible.
You can finally put away that bottle of Tylenol, because you’ll no longer get a migraine from RDM and ActiveX. Just call me Dr. Jenny, MD! (Hey, maybe I should get a TV series?)
As always, please let us know your thoughts by using the comment feature of the blog. You can also visit our forums to get help and submit feature requests, you can find them here.
Configuring the source tree
The next step is to configure the Apache source tree for your particular platform and personal requirements. This is done using the script
configure
included in the root directory of the distribution. (Developers downloading an unreleased version of the Apache source tree will need to have autoconf
and libtool
installed and will need to run buildconf
before proceeding with the next steps. This is not necessary for official releases.)To configure the source tree using all the default options, simply type
./configure
. To change the default options, configure
accepts a variety of variables and command line options.The most important option is the location
--prefix
where Apache is to be installed later, because Apache has to be configured for this location to work correctly. More fine-tuned control of the location of files is possible with additional configure options.Also at this point, you can specify which features you want included in Apache by enabling and disabling modules. Apache comes with a wide range of modules included by default. They will be compiled as shared objects (DSOs) which can be loaded or unloaded at runtime. You can also choose to compile modules statically by using the option
--enable-module=static
.Additional modules are enabled using the
--enable-module
option, where module is the name of the module with the mod_
string removed and with any underscore converted to a dash. Similarly, you can disable modules with the --disable-module
option. Be careful when using these options, since configure
cannot warn you if the module you specify does not exist; it will simply ignore the option.In addition, it is sometimes necessary to provide the
configure
script with extra information about the location of your compiler, libraries, or header files. This is done by passing either environment variables or command line options to configure
. For more information, see the configure
manual page. Or invoke configure
using the --help
option.For a short impression of what possibilities you have, here is a typical example which compiles Apache for the installation tree
/sw/pkg/apache
with a particular compiler and flags plus the two additional modules mod_ldap
and mod_lua
: $ CC='pgcc' CFLAGS='-O2'
./configure --prefix=/sw/pkg/apache
--enable-ldap=shared
--enable-lua=shared
When
configure
is run it will take several minutes to test for the availability of features on your system and build Makefiles which will later be used to compile the server.Build Rdm From Source For Mac Pro
![Download Download](/uploads/1/1/7/8/117843333/249615691.jpg)
Build Rdm From Source For Mac Computers
Details on all the different
configure
options are available on the configure
manual page.