# Calling linuxdeployqt with desktop file or binary

**URL:** <https://discourse.appimage.org/t/calling-linuxdeployqt-with-desktop-file-or-binary/330>\
**Category:** Creating AppImages\
**Created:** [April 21, 2018, 11:23am UTC](https://discourse.appimage.org/t/calling-linuxdeployqt-with-desktop-file-or-binary/330 "2018-04-21T11:23:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Silicomancer](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.appimage.org/silicomancer/32/133_2.png) [@Silicomancer](https://discourse.appimage.org/u/Silicomancer)\
**Post date:** [April 21, 2018, 11:23am UTC](https://discourse.appimage.org/t/calling-linuxdeployqt-with-desktop-file-or-binary/330/1 "2018-04-21T11:23:31Z")

</div>

When creating an AppImage, does it make any difference if linuxdeployqt is called with the .desktop file or with the application executable as a parameter?

---

<div class="post-metadata">

**Author:** ![probono](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.appimage.org/probono/32/81_2.png) [@probono](https://discourse.appimage.org/u/probono)\
**Post date:** [April 23, 2018, 6:23am UTC](https://discourse.appimage.org/t/calling-linuxdeployqt-with-desktop-file-or-binary/330/2 "2018-04-23T06:23:22Z")

</div>

It is recommended to run it with the desktop file as the parameter. The other option is for legacy backward compatibility.